Jan 04, 2016 These are different standards of C. By different standards I mean. New features adopted from other languages. Old features that are improved. Enhancement on security. Standardizing newly launched APIs Let me give you examples. Prior to C99 co. Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.
Technical Support
On-Line Manuals
Compiler User Guide
PrefaceOverview of the CompilerGetting Started with the CompilerCompiler FeaturesCompiler Coding PracticesCompiler Diagnostic MessagesUsing the Inline and Embedded Assemblers of the ARCompiler Command-line Options-Aopt--allow_fpreg_for_nonfpdata, --no_allow_fpreg_for_![Mode Mode](/uploads/1/2/5/7/125754114/740206965.png)
C99 Inline
-M--md--message_locale=lang_country[.codepage]--min_array_alignment=opt--mm--multibyte_chars, --no_multibyte_chars--multifile, --no_multifile--multiply_latency=cycles--narrow_volatile_bitfields--nonstd_qualifier_deduction, --no_nonstd_qualifie-o filename-Onum--old_specializations, --no_old_specializations--old_style_preprocessing--omf_browse--ool_section_name, --no_ool_section_name-Ospace-Otime--output_dir=directory_name-P--parse_templates, --no_parse_templates--pch--pch_dir=dir--pch_messages, --no_pch_messages--pch_verbose, --no_pch_verbose--pending_instantiations=n--phony_targets--pointer_alignment=num--preinclude=filename--preprocess_assembly--preprocessed--protect_stack, --no_protect_stack--reassociate_saturation, --no_reassociate_saturat--reduce_paths, --no_reduce_paths--remarks--remove_unneeded_entities, --no_remove_unneeded_e--restrict, --no_restrict--retain=option--rtti, --no_rtti--rtti_data, --no_rtti_data-S--share_inlineable_strings, --no_share_inlineable_--show_cmdline--signed_bitfields, --unsigned_bitfields--signed_chars, --unsigned_chars--split_ldm--split_sections--strict, --no_strict--strict_warnings--string_literal_pools, --no_string_literal_pools--sys_include--thumb--trigraphs, --no_trigraphs--type_traits_helpers, --no_type_traits_helpers-Uname--unaligned_access, --no_unaligned_access--use_frame_pointer, --no_use_frame_pointer--use_pch=filename--using_std, --no_using_std--version_number--vfe, --no_vfe--via=filename--vla, --no_vla--vsn-W--wchar, --no_wchar--wchar16--wchar32--whole_program--wrap_diagnostics, --no_wrap_diagnosticsLanguage ExtensionsCompiler-specific FeaturesC and C++ Implementation DetailsWhat is Semihosting?Via File Syntax![C99 C99](https://images2018.cnblogs.com/blog/1328928/201803/1328928-20180326231605049-1213209173.png)
Non-Confidential | PDF version | ARM DUI0375H | ||
|
7.20 --c99
Enables the compilation of C99 source code.
It enforces C only, and C++ syntax is not accepted.
Usage
This option can also be combined with other source language command-line options.
To ensure conformance with the ISO/IEC 9899:1999, the 1999 International Standard for C, you must also use the
--strict
option.Default
For files having a suffix of .c, .ac, or .tc,
--c90
applies by default.Only Allowed In C99 Mode
Related reference
Non-Confidential | PDF version | ARM DUI0375H |
Copyright © 2007, 2008, 2011, 2012, 2014-2016 ARM. All rights reserved. |
Related Knowledgebase Articles
ProductsDevelopment Tools | Hardware & Collateral | Downloads | Support | Contact |
Cookie Settings | Terms of Use | Privacy | Accessibility | Trademarks | Contact Us | Feedback Copyright © 2005-2019 Arm Limited (or its affiliates). All rights reserved. |