New GCC 5.0 Changes, Command-Line Options That Landed So Far

[phoronix]

Phoronix: New GCC 5.0 Changes, Command-Line Options That Landed So Far

While we're just a few months into the GCC 4.10 release cycle that's going to be released as GCC 5, there's already some release notes forming for this 2015 open-source compiler update...

http://www.phoronix.com/vr.php?view=MTc3MzE

[sdack]

One small but upcoming feature that I like is that gcc can be configured to generate instructions for a default target. The configure option "--with-arch=" will set the default and so one can have the compiler produce slightly better code without having to touch any Makefiles, setting environment variables or passing options to various configure and build scripts.

It is small, it is simple, but it is one of those things where you have to ask yourself: what took it so long?!

[turol]

Also in but not listed in changes yet are some warning options which will help you help the compiler devirtualize function calls

http://hubicka.blogspot.com/2014/08/devirtualization-in-c-part-5-asking.html

[curaga]

One small but upcoming feature that I like is that gcc can be configured to generate instructions for a default target. The configure option "--with-arch=" will set the default and so one can have the compiler produce slightly better code without having to touch any Makefiles, setting environment variables or passing options to various configure and build scripts.

It is small, it is simple, but it is one of those things where you have to ask yourself: what took it so long?!

Upcoming? I remember using that in 4.2 already.

[sdack]

Upcoming? I remember using that in 4.2 already.

No. You are thinking of the the "-march=" switch. I am talking about something new. A configure option to set the default.

[gilboa]

C: -Wno-incompatible-pointer-types

Hopefully it'll finally catch broken void **/void * conversions.

- Gilboa

[curaga]

No. You are thinking of the the "-march=" switch. I am talking about something new. A configure option to set the default.

Yes, I am talking about compile-time minimum cpu setting.

[curaga]

To be extra clear: GCC's compile-time minimum cpu setting.

[curaga]

Exhibit A: a commit from 2003 mentioning the configure option.

http://repo.or.cz/w/official-gcc.git/commit/7dd97ab62695cb000e76a6f7097a5ba9027aff9c

[sdack]

Exhibit A: a commit from 2003 mentioning the configure option.

http://repo.or.cz/w/official-gcc.git...7a5ba9027aff9c

Interesting. I have not seen the option before 4.10.