Show bugs on backlogs and boards — Azure DevOps, Microsoft Docs
Show bugs on backlogs and boards
- 1 Show bugs on backlogs and boards
- 2 Prerequisites
- 3 Set your team’s preferences for tracking bugs
- 4 Nested items
- 5 Add other work item types to your backlogs or boards
- 6 Create, list, and manage bugs
- 7 15 new features in iOS 13.2 that you should care about
- 8 Use Announce Messages with Siri
- 9 Opt-out feature of Siri and Dictation Improvement
- 10 Delete Previous Siri History
- 11 Use the new вЂEdit Home ScreenвЂ™ Feature
- 12 Delete Photos from within iMessage
- 13 Leverage the new вЂAirPlay and HandoffвЂ™ setting
- 14 Use the New Emojis in your communications
- 15 New emoji skin tone support feature in iOS 13.2
- 16 вЂRESEARCHвЂ™ provision in Privacy Settings
- 17 Apps with new Share sheet functions
- 18 iOS 13.2 offers a few exclusive features for iPhone 11/ 11 Pro users
- 19 Other iOS 13.2 Notable features
- 20 GCC 4.5 Release SeriesChanges, New Features, and Fixes
- 21 Caveats
- 22 General Optimizer Improvements
- 23 New Languages and Language specific improvements
- 24 New Targets and Target Specific Improvements
- 25 Operating Systems
- 26 Other significant improvements
- 27 GCC 4.5.1
- 28 GCC 4.5.2
- 29 GCC 4.5.3
- 30 GCC 4.5.4
Azure Boards | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013
As your team identifies code defects or bugs, they can add them to the backlog and track them similar to requirements. Or, they can schedule them to be fixed within a sprint along with other tasks.
You can define this team setting for the Agile, Scrum, and CMMI processes. The Bug work item type isn’t defined for the Basic process, so there isn’t a team setting for Basic. Instead, you should track bugs and code defects using the Issue work item type.
When you track bugs as requirements, they’ll show up on the product backlog and Kanban board. When you track bugs similar to tasks, they’ll show up on the sprint backlogs and task boards. If you want to track additional work item types (WITs) or custom WITs on your backlogs or boards, you can. See Add other work item types to backlogs or boards later in this topic.
- To configure team settings, you must be added as a team administrator or be a member of the Project Administrators or Project Collection Administrators group. See Set permissions at the project- or collection-level.
Set your team’s preferences for tracking bugs
You can change the setting from a backlog or board view. Here we show how to change it from the board view.
In the Working with bugs dialog, you can select from the following three options.
Choose the first option when your team wants to manage bugs similar to requirements. Bugs can be estimated and tracked against team velocity and cumulative flow. Bugs are associated with the Requirements category.
Choose the second option when your team wants to manage bugs similar to tasks. Remaining work can be tracked for bugs and tracked against the sprint capacity and burndown. Bugs are associated with the Task category.
Choose the last option if your team manages bugs separate from requirements or tasks. Bugs are associated with the Bugs category and won’t appear on either backlogs or boards.
Open your Kanban board. If you’re not a team admin, get added as one. Only team and project admins can customize the Kanban board.
Choose the gear icon to configure the board and set general team settings.
Choose Working with bugs and then choose the option that best meets your team’s way of working.
When you’re done with your changes, choose Save.
To see the changes, open or refresh the team’s backlog or Kanban board.
Open your Kanban board. If you’re not a team admin, get added as one. Only team and project admins can customize the Kanban board.
Choose the gear icon to open the settings dialog.
Choose Working with bugs and then choose the option that best meets your team’s way of working.
When done with your changes, choose Save.
To see the changes, open or refresh your team’s backlog or Kanban board.
Requires TFS 2013.4 or later version.
Open your team settings from the Overview tab of your team’s admin context. Your changes are automatically saved.
Choose the , (gear icon) to open the administration page.
From the Overview tab, choose the team whose settings you want to configure, and then choose Settings. Select the option you want. Your changes are automatically saved.
To see the changes, open or refresh the team’s backlog or Kanban board.
If, after refreshing a backlog or board, and you don’t see bugs where you expect them, review How backlogs and boards display hierarchical (nested) items. Only leaf nodes of nested items appear on the Kanban or task boards.
When you manage bugs with requirements or with tasks, they’ll show up on one or more of your Agile tool backlogs and boards. However, if you nest itemsвЂ”create parent-child links of items that belong in either the Requirements or Task categoriesвЂ”then not all items may appear on your backlogs and boards. To learn more about how nested items are treated, see How backlogs and boards display hierarchical (nested) items.
Add other work item types to your backlogs or boards
Bugs are a common item that teams want to track, and choose how they track it. See Manage bugs for more guidance.
However, what if you want to track other work item types (WITs) on your backlogs and boards?
You can add other WITsвЂ”such as change requests, issues, or impedimentsвЂ” by customizing your process or project, based on the process model you use. For details,
You can add other WITsвЂ”such as change requests, issues, or impedimentsвЂ” by customizing your process or project, based on the process model you use. For details, see Add a work item type to a backlog and board.
Create, list, and manage bugs
When bugs are managed along with requirements, you can add them through the product backlog or Kanban board. When bugs are managed along with tasks, you can add them to a sprint backlog or taskboard. Or, you can capture them using other tools as indicated in Define, triage, and manage bugs.
You can review bugs defined for your project by creating a query and specifying the Work Item Type=Bug. Or, open a predefined query, Active Bugs (Agile and CMMI) or Work in Progress (Scrum). For other bug related tasks, see the following articles:
15 new features in iOS 13.2 that you should care about
By SK 6 comments Last updated October 28, 2019
Apple has released iOS 13.2 along with the release of the new AirPods Pro today. The new iOS comes after three interim rounds of iOS 13.1 and brings many new features apart from attempting to fix some of the bugs from prior releases.
Although there are a lot of changes with iOS 13.2 we look at the top 15 new features and changes in iOS 13.2 that you should care about the most:
Use Announce Messages with Siri
Users with Apple AirPods 2 and later (hoping that the new AirPods are released on Oct 30th) will be able to use this new announce with Siri feature. In order to set this up, follow these steps.
- Open Settings on your iPhone or iPad
- Tap Notifications.
- Tap Announce Messages with Siri.
- Slide the switch next to Announce Messages with Siri to the ON position.
This new feature for the AirPods works pretty well and consistently. If you encounter any issues, be sure to check out our tips article below.
There is also now a new notification sound associated with these notifications in iOS 13.2. If you have any issues setting up and using this new feature with your AirPods, check out the various tips that we have outlined below.
Opt-out feature of Siri and Dictation Improvement
iOS 13.2 addresses usersвЂ™ concerns about Siri and dictation privacy. When you set this up, Apple will not use any data collected from your device ( Siri and dictation) for its internal analysis. In order to do this, follow these steps:
- Tap on Settings > Privacy > Analytics & Improvements
- Disable вЂImprove Siri & DictationвЂ™
One had to go through a few hoops and loops prior to the release of this feature in order to reduce sharing data with Siri
Delete Previous Siri History
You can use this new feature to delete Siri history in order to protect privacy concerns. We feel AppleвЂ™s privacy setup is pretty solid, if however you are concerned, hereвЂ™s how to remove your Siri history.
- Tap on Settings > Siri & Search
- Tap on Siri & Dictation History
- Choose Delete Siri and Dictation history
Please note that this option to delete Siri and Dictation history will only show up if you have вЂImprove Siri and DictationвЂ™ enabled on your device.
Use the new вЂEdit Home ScreenвЂ™ Feature
To delete apps or rearrange apps with ease, Apple changed the quick action language from re-arrange apps to edit the home screen. Many users found re-arranging apps on the home screen to be a very unintuitive process when iOS 13 was released. Apple has addressed this issue in iOS 13.2. Here is how you delete apps or re-arrange apps on your Home Screen:
- Tap on any app and hold
- Select вЂDelete AppвЂ™ to delete the individual app
Use Edit Home screen to re-arrange apps or delete apps by using the menu item.
Delete Photos from within iMessage
Many users struggled with the iOS 13 change that required one to go to iPhone Storage Settings and manage photos and documents from there. The old iOS 12 feature where you click on the вЂiвЂ™ icon and review photos, select multiple photos and delete them is now back with iOS 13.2. It works the same way as in iOS 12.
- Tap on the Contact name at the top of the message
- Select the вЂiвЂ™ icon and let the Photos load up
- Select one or Multiple Photos and choose Delete
Leverage the new вЂAirPlay and HandoffвЂ™ setting
Use these settings to transfer to a HomePod. When playing a song, just bring your iPhone close to the top of your HomePod to transfer whatвЂ™s playing on your iPhone.
There is also a new setting in the Handoff section that you can use to disable the automatic airplay to TVs.
Use the New Emojis in your communications
iOS 13.2 introduces many new emojis including the new otter emoji, ringed planet, beverage box, pinching hands emoji and more importantly a host of emojis to support accessibility options such as a wheelchair, service dog support, and others.
Some of these new emojis were approved via the Emoji 12.0 update that was released earlier this year and is now being adopted by Apple via iOS 13.2
New emoji skin tone support feature in iOS 13.2
You can now easily select multiple skin tones for a single emoji when typing your messages. This works for most of the emoji icons that are hand based. Thumps-up, Thumbs down and so on.
Press the emoji icon and hold for a second and choose between the different skin tones to use.
вЂRESEARCHвЂ™ provision in Privacy Settings
If you decide to participate in the new Apple Health research programs launching later, you will need to install the related apps from the App Store. You will be able to control the privacy settings for these apps from here.
- Tap on Settings > Privacy
- Next tap on вЂRESEARCHвЂ™
Apps that have new share sheet integration prominently show up in your share-sheet.
This is useful as it automatically integrates third-party app features into your share sheet making it easier to use the functions.
iOS 13.2 offers a few exclusive features for iPhone 11/ 11 Pro users
These are primarily related to the Camera function. If you are an iPhone 11 Pro user, you will find these exciting features very helpful.
Take Advantage of the Deep Fusion feature
iOS 13.2 introduces the new Deep Fusion feature. This is a new image processing system enabled by the Neural Engine of A13 Bionic in iPhone 11 pro models.
Deep Fusion uses advanced machine learning to do pixel-by-pixel processing of photos, optimizing for texture, details and noise in every part of the photo.
Change Frame Rate and Resolution from within the Camera app
The new iOS 13.2 offers a major enhancement for iPhone 11 users. This has been a major request from users for quite some time now. It is nice to see Apple take care of this in iOS 13.2
You can now access and change frame rate and set up photo resolution directly from the Camera app. No more switching between the Settings App and Camera app.
YouTube App supports HDR Playback
feature for the iPhone 11 Models. This was already available for the older iPhones and now has been made available for the iPhone 11 models. ( Not necessarily an iOS 13.2 feature, since its Google, that enables or disables this feature for devices running their app)
Other iOS 13.2 Notable features
Some of the other notable features available on iOS 13.2 include dark mode support for the FaceBook app, new shutter sound in the night mode camera, new icons to represent AirPods in the volume widget on the control center along with a much better and integrates Siri support for third party messaging apps such as WhatsApp.
Finally, the iOS 13.2 fixes many of the bugs related with the prior iOS versions including some of the common ones related to the Mail app. In our testing, we have found that the battery holds up pretty well and noticed the improved RAM management functions. Apps feel more snappier overall.
In order to update your iPhone to the latest iOS 13.2, tap on Settings > General > Software Update. Once the new release is available and you are unable to find it on your iPhone, disable your Wi-Fi and then enable it and then try and see if the new update shows up on your device.
What are some of the features you would like to see in the future iOS releases?
Obsessed with tech since the early arrival of A/UX on Apple, Sudz (SK) is responsible for the editorial direction of AppleToolBox. He is based out of Los Angeles, CA.
Sudz specializes in covering all things macOS, having reviewed dozens of OS X and macOS developments over the years.
In a former life, Sudz worked helping Fortune 100 companies with their technology and business transformation aspirations.
GCC 4.5 Release Series
Changes, New Features, and Fixes
GCC now requires the MPC library in order to build. See the prerequisites page for version requirements.
Support for a number of older systems and recently unmaintained or untested target ports of GCC has been declared obsolete in GCC 4.5. Unless there is activity to revive them, the next release of GCC will have their sources permanently removed.
The following ports for individual systems on particular architectures have been obsoleted:
- IRIX releases before 6.5 (mips-sgi-irix5*, mips-sgi-irix6.[0-4])
- Solaris 7 (*-*-solaris2.7)
- Tru64 UNIX releases before V5.1 (alpha*-dec-osf4*, alpha-dec-osf5.0*)
- Details for the IRIX, Solaris 7, and Tru64 UNIX obsoletions can be found in the announcement.
Support for the classic POWER architecture implemented in the original RIOS and RIOS2 processors of the old IBM RS/6000 product line has been obsoleted in the rs6000 port. This does not affect the new generation Power and PowerPC architectures.
General Optimizer Improvements
- The -save-temps now takes an optional argument. The -save-temps and -save-temps=cwd switches write the temporary files in the current working directory based on the original source file. The -save-temps=obj switch will write files into the directory specified with the -o option, and the intermediate filenames are based on the output file. This will allow the user to get the compiler intermediate files when doing parallel builds without two builds of the same filename located in different directories from interfering with each other.
- Debugging dumps are now created in the same directory as the object file rather than in the current working directory. This allows the user to get debugging dumps when doing parallel builds without two builds of the same filename interfering with each other.
- GCC has been integrated with the MPC library. This allows GCC to evaluate complex arithmetic at compile time more accurately. It also allows GCC to evaluate calls to complex built-in math functions having constant arguments and replace them at compile time with their mathematically equivalent results. In doing so, GCC can generate correct results regardless of the math library implementation or floating point precision of the host platform. This also allows GCC to generate identical results regardless of whether one compiles in native or cross-compile configurations to a particular target. The following built-in functions take advantage of this new capability: cacos , cacosh , casin , casinh , catan , catanh , ccos , ccosh , cexp , clog , cpow , csin , csinh , csqrt , ctan , and ctanh . The float and long double variants of these functions (e.g. csinf and csinl ) are also handled.
- A new link-time optimizer has been added ( -flto ). When this option is used, GCC generates a bytecode representation of each input file and writes it to specially-named sections in each object file. When the object files are linked together, all the function bodies are read from these named sections and instantiated as if they had been part of the same translation unit. This enables interprocedural optimizations to work across different files (and even different languages), potentially improving the performance of the generated code. To use the link-timer optimizer, -flto needs to be specified at compile time and during the final link. If the program does not require any symbols to be exported, it is possible to combine -flto and the experimental -fwhopr with -fwhole-program to allow the interprocedural optimizers to use more aggressive assumptions.
- The automatic parallelization pass was enhanced to support parallelization of outer loops.
- Automatic parallelization can be enabled as part of Graphite. In addition to -ftree-parallelize-loops= , specify -floop-parallelize-all to enable the Graphite-based optimization.
- The infrastructure for optimizing based on restrict qualified pointers has been rewritten and should result in code generation improvements. Optimizations based on restrict qualified pointers are now also available when using -fno-strict-aliasing .
- There is a new optimization pass that attempts to change prototype of functions to avoid unused parameters, pass only relevant parts of structures and turn arguments passed by reference to arguments passed by value when possible. It is enabled by -O2 and above as well as -Os and can be manually invoked using the new command-line switch -fipa-sra .
- GCC now optimize exception handling code. In particular cleanup regions that are proved to not have any effect are optimized out.
New Languages and Language specific improvements
- The -fshow-column option is now on by default. This means error messages now have a column associated with them.
- Compilation of programs heavily using discriminated record types with variant parts has been sped up and generates more compact code.
- Stack checking now works reasonably well on most plaforms. In some specific cases, stack overflows may still fail to be detected, but a compile-time warning will be issued for these cases.
- If a header named in a #include directive is not found, the compiler exits immediately. This avoids a cascade of errors arising from declarations expected to be found in that header being missing.
- A new built-in function __builtin_unreachable() has been added that tells the compiler that control will never reach that point. It may be used after asm statements that terminate by transferring control elsewhere, and in other places that are known to be unreachable.
- The -Wlogical-op option now warns for logical expressions such as (c == 1 && c == 2) and (c != 1 || c != 2) , which are likely to be mistakes. This option is disabled by default.
- An asm goto feature has been added to allow asm statements that jump to C labels.
- C++0x raw strings are supported for C++ and for C with -std=gnu99 .
- The deprecated attribute now takes an optional string argument, for example, __attribute__((deprecated(«text string»))) , that will be printed together with the deprecation warning.
- The -Wenum-compare option, which warns when comparing values of different enum types, now works for C. It formerly only worked for C++. This warning is enabled by -Wall . It may be avoided by using a type cast.
- The -Wcast-qual option now warns about casts which are unsafe in that they permit const-correctness to be violated without further warnings. Specifically, it warns about cases where a qualifier is added when all the lower types are not const . For example, it warns about a cast from char ** to const char ** .
- The -Wc++-compat option is significantly improved. It issues new warnings for:
- Using C++ reserved operator names as identifiers.
- Conversions to enum types without explicit casts.
- Using va_arg with an enum type.
- Using different enum types in the two branches of ?: .
- Using ++ or — on a variable of enum type.
- Using the same name as both a struct, union or enum tag and a typedef, unless the typedef refers to the tagged type itself.
- Using a struct, union, or enum which is defined within another struct or union.
- A struct field defined using a typedef if there is a field in the struct, or an enclosing struct, whose name is the typedef name.
- Duplicate definitions at file scope.
- Uninitialized const variables.
- A global variable with an anonymous struct, union, or enum type.
- Using a string constant to initialize a char array whose size is the length of the string.
- The new -Wjump-misses-init option warns about cases where a goto or switch skips the initialization of a variable. This sort of branch is an error in C++ but not in C. This warning is enabled by -Wc++-compat .
- GCC now ensures that a C99-conforming is present on most targets, and uses information about the types in this header to implement the Fortran bindings to those types. GCC does not ensure the presence of such a header, and does not implement the Fortran bindings, on the following targets: NetBSD, VxWorks, VMS, SymbianOS, WinCE, LynxOS, Netware, QNX, Interix, TPF.
- GCC now implements C90- and C99-conforming rules for constant expressions. This may cause warnings or errors for some code using expressions that can be folded to a constant but are not constant expressions as defined by ISO C.
- All known target-independent C90 and C90 Amendment 1 conformance bugs, and all known target-independent C99 conformance bugs not related to floating point or extended identifiers, have been fixed.
- The C decimal floating point support now includes support for the FLOAT_CONST_DECIMAL64 pragma.
- The named address space feature from ISO/IEC TR 18037 is now supported. This is currently only implemented for the SPU processor.
- Improved experimental support for the upcoming C++0x ISO C++ standard, including support for raw strings, lambda expressions and explicit type conversion operators.
- When printing the name of a class template specialization, G++ will now omit any template arguments which come from default template arguments. This behavior (and the pretty-printing of function template specializations as template signature and arguments) can be disabled with the -fno-pretty-templates option.
- Access control is now applied to typedef names used in a template, which may cause G++ to reject some ill-formed code that was accepted by earlier releases. The -fno-access-control option can be used as a temporary workaround until the code is corrected.
- Compilation time for code that uses templates should now scale linearly with the number of instantiations rather than quadratically, as template instantiations are now looked up using hash tables.
- Declarations of functions that look like builtin declarations of library functions are only considered to be redeclarations if they are declared with extern «C». This may cause problems with code that omits extern «C» on hand-written declarations of C library functions such as abort or memcpy . Such code is ill-formed, but was accepted by earlier releases.
- Diagnostics that used to complain about passing non-POD types to . or jumping past the declaration of a non-POD variable now check for triviality rather than PODness, as per C++0x.
- In C++0x mode local and anonymous classes are now allowed as template arguments, and in declarations of variables and functions with linkage, so long as any such declaration that is used is also defined (DR 757).
- Labels may now have attributes, as has been permitted for a while in C. This is only permitted when the label definition and the attribute specifier is followed by a semicolon—i.e., the label applies to an empty statement. The only useful attribute for a label is unused .
- G++ now implements DR 176. Previously G++ did not support using the injected-class-name of a template base class as a type name, and lookup of the name found the declaration of the template in the enclosing scope. Now lookup of the name finds the injected-class-name, which can be used either as a type or as a template, depending on whether or not the name is followed by a template argument list. As a result of this change, some code that was previously accepted may be ill-formed because
- The injected-class-name is not accessible because it’s from a private base, or
- The injected-class-name cannot be used as an argument for a template template parameter.
In either of these cases, the code can be fixed by adding a nested-name-specifier to explicitly name the template. The first can be worked around with -fno-access-control ; the second is only rejected with -pedantic .
- A new standard mangling for SIMD vector types has been added, to avoid name clashes on systems with vectors of varying length. By default the compiler still uses the old mangling, but emits aliases with the new mangling on targets that support strong aliases. Users can switch over entirely to the new mangling with -fabi-version=4 or -fabi-version=0 . -Wabi will now warn about code that uses the old mangling.
- The command-line option -ftemplate-depth-N is now written as -ftemplate-depth=N and the old form is deprecated.
- Conversions between NULL and non-pointer types are now warned by default. The new option -Wno-conversion-null disables these warnings. Previously these warnings were only available when using -Wconversion explicitly.
Runtime Library (libstdc++)
- Improved experimental support for the upcoming ISO C++ standard, C++0x, including:
- Support for , , and .
- Existing facilities now exploit explicit operators and the newly implemented core C++0x features.
- The header has been renamed to .
An experimental profile mode has been added. This is an implementation of many C++ standard library constructs with an additional analysis layer that gives performance improvement advice based on recognition of suboptimal usage patterns. For example,
When instrumented via the profile mode, can return suggestions about the initial size and choice of the container used as follows:
These constructs can be substituted for the normal libstdc++ constructs on a piecemeal basis, or all existing components can be transformed via the -D_GLIBCXX_PROFILE macro.
- Support for decimal floating-point arithmetic (aka ISO C++ TR 24733) has been added. This support is in header file , uses namespace std::decimal , and includes classes decimal32 , decimal64 , and decimal128 .
- Sources have been audited for application of function attributes nothrow , const , pure , and noreturn .
- Python pretty-printers have been added for many standard library components that simplify the internal representation and present a more intuitive view of components when used with appropriately-advanced versions of GDB. For more information, please consult the more detailed description.
- The default behavior for comparing typeinfo names has changed, so in , __GXX_MERGED_TYPEINFO_NAMES now defaults to zero.
- The new -static-libstdc++ option directs g++ to link the C++ library statically, even if the default would normally be to link it dynamically.
- The COMMON default padding has been changed – instead of adding the padding before a variable it is now added afterwards, which increases the compatibility with other vendors and helps to obtain the correct output in some cases. Cf. also the -falign-commons option (added in 4.4).
- The -finit-real= option now also supports the value snan for signaling not-a-number; to be effective, one additionally needs to enable trapping (e.g. via -ffpe-trap= ). Note: Compile-time optimizations can turn a signaling NaN into a quiet one.
- The new option -fcheck= has been added with the options bounds , array-temps , do , pointer , and recursive . The bounds and array-temps options are equivalent to -fbounds-check and -fcheck-array-temporaries . The do option checks for invalid modification of loop iteration variables, and the recursive option tests for recursive calls to subroutines/functions which are not marked as recursive. With pointer pointer association checks in calls are performed; however, neither undefined pointers nor pointers in expressions are handled. Using -fcheck=all enables all these run-time checks.
- The run-time checking -fcheck=bounds now warns about invalid string lengths of character dummy arguments. Additionally, more compile-time checks have been added.
- The new option -fno-protect-parens has been added; if set, the compiler may reorder REAL and COMPLEX expressions without regard to parentheses.
- GNU Fortran no longer links against libgfortranbegin . As before, MAIN__ (assembler symbol name) is the actual Fortran main program, which is invoked by the main function. However, main is now generated and put in the same object file as MAIN__ . For the time being, libgfortranbegin still exists for backward compatibility. For details see the new Mixed-Language Programming chapter in the manual.
- The I/O library was restructured for performance and cleaner code.
- Array assignments and WHERE are now run in parallel when OpenMP’s WORKSHARE is used.
- The experimental option -fwhole-file was added. The option allows whole-file checking of procedure arguments and allows for better optimizations. It can also be used with -fwhole-program , which is now also supported in gfortran.
- More Fortran 2003 and Fortran 2008 mathematical functions can now be used as initialization expressions.
- Some extended attributes such as STDCALL are now supported via the GCC$ compiler directive.
- For Fortran 77 compatibility: If -fno-sign-zero is used, the SIGN intrinsic behaves now as if zero were always positive.
- For legacy compatibiliy: On Cygwin and MinGW, the special files CONOUT$ and CONIN$ (and CONERR$ which maps to CONOUT$ ) are now supported.
- Fortran 2003 support has been extended:
- Procedure-pointer function results and procedure-pointer components (including PASS),
- allocatable scalars (experimental),
- DEFERRED type-bound procedures,
- the ERRMSG= argument of the ALLOCATE and DEALLOCATE statements have been implemented.
- The ALLOCATE statement supports type-specs and the SOURCE= argument.
- OPERATOR(*) and ASSIGNMENT(=) are now allowed as GENERIC type-bound procedure (i.e. as type-bound operators).
- Rounding ( ROUND= , RZ , . ) for output is now supported.
- The INT_FAST<8,16,32,64,128>_T kind type parameters of the intrinsic module ISO_C_BINDING are now supported, except for the targets listed above as ones where GCC does not have type information.
- Extensible derived types with type-bound procedure or procedure pointer with PASS attribute now have to use CLASS in line with the Fortran 2003 standard; the workaround to use TYPE is no longer supported.
- Experimental, incomplete support for polymorphism, including CLASS , SELECT TYPE and dynamic dispatch of type-bound procedure calls. Some features do not work yet such as unlimited polymorphism ( CLASS(*) ).
- Fortran 2008 support has been extended:
- The OPEN statement now supports the NEWUNIT= option, which returns a unique file unit, thus preventing inadvertent use of the same unit in different parts of the program.
- Support for unlimited format items has been added.
- The INT <8,16,32>and REAL <32,64,128>kind type parameters of the intrinsic module ISO_FORTRAN_ENV are now supported.
- Using complex arguments with TAN , SINH , COSH , TANH , ASIN , ACOS , and ATAN is now possible; the functions ASINH , ACOSH , and ATANH have been added (for real and complex arguments) and ATAN(Y,X) is now an alias for ATAN2(Y,X).
- The BLOCK construct has been implemented.
New Targets and Target Specific Improvements
- Full cross-toolchain support now available with GNU Binutils
- GCC now supports the Cortex-M0 and Cortex-A5 processors.
- GCC now supports the ARM v7E-M architecture.
- GCC now supports VFPv4-based FPUs and FPUs with single-precision-only VFP.
- GCC has many improvements to optimization for other ARM processors, including scheduling support for the integer pipeline on Cortex-A9.
- GCC now supports the IEEE 754-2008 half-precision floating-point type, and a variant ARM-specific half-precision type. This type is specified using __fp16 , with the layout determined by -mfp16-format . With appropriate -mfpu options, the Cortex-A9 and VFPv4 half-precision instructions will be used.
- GCC now supports the variant of AAPCS that uses VFP registers for parameter passing and return values.
- The -mno-tablejump option has been removed because it has the same effect as the -fno-jump-tables option.
- Added support for these new AVR devices:
- GCC now will set the default for -march= based on the configure target.
- GCC now supports handling floating-point excess precision arising from use of the x87 floating-point unit in a way that conforms to ISO C99. This is enabled with -fexcess-precision=standard and with standards conformance options such as -std=c99 , and may be disabled using -fexcess-precision=fast .
- Support for the Intel Atom processor is now available through the -march=atom and -mtune=atom options.
- A new -mcrc32 option is now available to enable crc32 intrinsics.
- A new -mmovbe option is now available to enable GCC to use the movbe instruction to implement __builtin_bswap32 and __builtin_bswap64 .
- SSE math now can be enabled by default at configure time with the new —with-fpmath=sse option.
- There is a new intrinsic header file, . It should be included before using any IA-32/x86-64 intrinsics.
- Support for the XOP, FMA4, and LWP instruction sets for the AMD Orochi processors are now available with the -mxop , -mfma4 , and -mlwp options.
- The -mabm option enables GCC to use the popcnt and lzcnt instructions on AMD processors.
- The -mpopcnt option enables GCC to use the popcnt instructions on both AMD and Intel processors.
- GCC now supports ColdFire 51xx, 5221x, 5225x, 52274, 52277, 5301x and 5441x devices.
- GCC now supports thread-local storage (TLS) on M68K and ColdFire processors.
Support has been added for the Toshiba Media embedded Processor (MeP, or mep-elf) embedded target.
- GCC now supports MIPS 1004K processors.
- GCC can now be configured with options —with-arch-32 , —with-arch-64 , —with-tune-32 and —with-tune-64 to control the default optimization separately for 32-bit and 64-bit modes.
- MIPS targets now support an alternative _mcount interface, in which register $12 points to the function’s save slot for register $31 . This interface is selected by the -mcount-ra-address option; see the documentation for more details.
- GNU/Linux targets can now generate read-only .eh_frame sections. This optimization requires GNU binutils 2.20 or above, and is only available if GCC is configured with a suitable version of binutils.
- GNU/Linux targets can now attach special relocations to indirect calls, so that the linker can turn them into direct jumps or branches. This optimization requires GNU binutils 2.20 or later, and is automatically selected if GCC is configured with an appropriate version of binutils. It can be explicitly enabled or disabled using the -mrelax-pic-calls command-line option.
- GCC now generates more heavily-optimized atomic operations on Octeon processors.
- MIPS targets now support the -fstack-protector option.
- GCC now supports an -msynci option, which specifies that synci is enough to flush the instruction cache, without help from the operating system. GCC uses this information to optimize automatically-generated cache flush operations, such as those used for nested functions in C. There is also a —with-synci configure-time option, which makes -msynci the default.
- GCC supports four new function attributes for interrupt handlers: interrupt , use_shadow_register_set , keep_interrupts_masked and use_debug_exception_return . See the documentation for more details about these attributes.
- GCC now supports the Power ISA 2.06, which includes the VSX instructions that add vector 64-bit floating point support, new population count instructions, and conversions between floating point and unsigned types.
- Support for the power7 processor is now available through the -mcpu=power7 and -mtune=power7 .
- GCC will now vectorize loops that contain simple math functions like copysign when generating code for altivec or VSX targets.
- Support for the A2 processor is now available through the -mcpu=a2 and -mtune=a2 options.
- Support for the 476 processor is now available through the -mcpu= <476,476fp>and -mtune= <476,476fp>options.
- Support for the e500mc64 processor is now available through the -mcpu=e500mc64 and -mtune=e500mc64 options.
- GCC can now be configured with options —with-cpu-32 , —with-cpu-64 , —with-tune-32 and —with-tune-64 to control the default optimization separately for 32-bit and 64-bit modes.
- Starting with GCC 4.5.4, vectors of type vector long long or vector long are passed and returned in the same method as other vectors with the VSX instruction set. Previously the GCC compiler did not adhere to the ABI for 128-bit vectors with 64-bit integer base types (PR 48857). This is also fixed in the GCC 4.6.1 release.
Support has been added for the Renesas RX Processor (rx-elf) target.
Windows (Cygwin and MinGW)
- GCC now installs all the major language runtime libraries as DLLs when configured with the —enable-shared option.
- GCC now makes use of the new support for aligned common variables in versions of binutils >= 2.20 to fix bugs in the support for SSE data types.
- Improvements to the libffi support library increase the reliability of code generated by GCJ on all Windows platforms. Libgcj is enabled by default for the first time.
- Libtool improvements simplify installation by placing the generated DLLs in the correct binaries directory.
- Numerous other minor bugfixes and improvements, and substantial enhancements to the Fortran language support library.
Other significant improvements
- It is now possible to extend the compiler without having to modify its source code. A new option -fplugin=file.so tells GCC to load the shared object file.so and execute it as part of the compiler. The internal documentation describes the details on how plugins can interact with the compiler.
- The move to newer autotools changed default installation directories and switches to control them: The —with-datarootdir , —with-docdir , —with-pdfdir , and —with-htmldir switches are not used any more. Instead, you can now use —datarootdir , —docdir , —htmldir , and —pdfdir . The default installation directories have changed as follows according to the GNU Coding Standards:
datarootdir read-only architecture-independent data root [PREFIX/share] localedir locale-specific message catalogs [DATAROOTDIR/locale] docdir documentation root [DATAROOTDIR/doc/PACKAGE] htmldir html documentation [DOCDIR] dvidir dvi documentation [DOCDIR] pdfdir pdf documentation [DOCDIR] psdir ps documentation [DOCDIR]
The following variables have new default values:
datadir read-only architecture-independent data [DATAROOTDIR] infodir info documentation [DATAROOTDIR/info] mandir man documentation [DATAROOTDIR/man]
This is the list of problem reports (PRs) from GCC’s bug tracking system that are known to be fixed in the 4.5.1 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here).
GCC’s new link-time optimizer ( -flto ) now also works on a few non-ELF targets:
- Cygwin (*-cygwin*)
- MinGW (*-mingw*)
- Darwin on x86-64 (x86_64-apple-darwin*)
LTO is not enabled by default for these targets. To enable LTO, you should configure with the —enable-lto option.
This is the list of problem reports (PRs) from GCC’s bug tracking system that are known to be fixed in the 4.5.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here).
This is the list of problem reports (PRs) from GCC’s bug tracking system that are known to be fixed in the 4.5.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here).
On the PowerPC compiler, the Altivec builtin functions vec_ld and vec_st have been modified to generate the Altivec memory instructions LVX and STVX , even if the -mvsx option is used. In the initial GCC 4.5 release, these builtin functions were changed to generate VSX memory reference instructions instead of Altivec memory instructions, but there are differences between the two instructions. If the VSX instruction set is available, you can now use the new builtin functions vec_vsx_ld and vec_vsx_st which always generates the VSX memory instructions.
This is the list of problem reports (PRs) from GCC’s bug tracking system that are known to be fixed in the 4.5.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here).
Copyright (C) Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
These pages are maintained by the GCC team. Last modified 2019-11-28 .