Re: diag color

2016-07-31 Thread phi gcc
Hi, Well, I can't 'easilly' change the makefiles I am using, they are not mine,meaning I would have to 'patch' any build env Makefile each time we do a refresh of the app sources. Then some gcc version don't understand the -fno-diagnostics-color meaning the makefile patch would have to be GCC vers

Re: diag color

2016-07-31 Thread Markus Trippelsdorf
On 2016.07.31 at 10:46 +0200, phi gcc wrote: > While a simple getenv("TERM") to setup the default of the color > predicate before going to the sequence of testing CFLAGS, et the > optargs, would cost almost nothing. If you want a full explanation of the current behavior please read the comments in

Re: diag color

2016-07-31 Thread Jonathan Wakely
On 31 July 2016 at 07:08, phi gcc wrote: > Hi All, > > Reposting this here from gcc-help. > > > I got the impression that I got colors in diag output depsite the fact > that I got no GCC env var setup. The manual says "Setting GCC_COLORS to the empty string disables colors." Did you try that? Set

Re: diag color

2016-07-31 Thread phi gcc
Hi Jon, On Sun, Jul 31, 2016 at 1:16 PM, Jonathan Wakely > The manual says "Setting GCC_COLORS to the empty string disables colors." > > Did you try that? Setting it to an empty string in your env should > disable the coloured output. Yes it works, sounds a less intrusive one :) regarding old ver

Re: diag color

2016-07-31 Thread phi gcc
Forgot to say that before posting I did try export GCC_COLORS=never after reading == -fno-diagnostics-colorUse color in diagnostics. WHEN is ‘never’, ‘always’, or ‘auto’. The default depends on how the compiler has been configured, it can be any of the above WHEN options or also ‘never’ if GC

Re: diag color

2016-07-31 Thread Manuel López-Ibáñez
On 31/07/16 13:16, phi gcc wrote: I admit I red this a bit too fast, and since the doc sez "if GCC_COLORS isn't present" I didn't infered what it does if set. I didn't saw the =never was a goof for the env var. I guess I must not be the only one trapped here. Yet I still believe it is wrongly c

Re: Two suggestions for gcc C compiler to extend C language (by WD Smith)

2016-07-31 Thread David Brown
On 29/07/16 18:26, Warren D Smith wrote: Booleans are very useful - they turn up all over the place in programming. Nibbles, on the other hand, are almost totally useless. There are very, very few situations where you need to store a number that is within the range 0 .. 15, and are so tightly c

Re: diag color

2016-07-31 Thread phi gcc
Hi Manuel, On Sun, Jul 31, 2016 at 3:16 PM, Manuel López-Ibáñez wrote: > On 31/07/16 13:16, phi gcc wrote: > > If you think you can code it better, prove it: Why should I ? I am not a gcc designer, just humbelly reporting a usability issue, where a gcc upgrade start to produce garbled unreadabl

Re: diag color

2016-07-31 Thread phi gcc
On Sun, Jul 31, 2016 at 10:54 PM, phi gcc wrote: > If this is still accepted as a potential problem then lemme know the official > process to submit a bug report. I oppsed here, I red your link and see the very last line about bugzilla will experiment this...

Re: Question about find modifiable mems

2016-07-31 Thread shmeel gutl
On 03-Jun-15 09:39 AM, shmeel gutl wrote: find_modifiable_mems was introduced to gcc 4.8 in september 2012. Is there any documentation as to how it is supposed to help the haifa scheduler? In my private port of gcc it make the following type of transformations from a= *(b+20)

Re: diag color

2016-07-31 Thread phi gcc
bugzilla don't likes me, can't get in Ok let's forget participation then...

Re: diag color

2016-07-31 Thread Jonathan Wakely
On 31 July 2016 at 22:06, phi gcc wrote: > bugzilla don't likes me, can't get in > Ok let's forget participation then... We were attacked by spammers last week and had to temporarily disable account creation. The notice you got from bugzilla should have given the details of an admin to contact

Re: diag color

2016-07-31 Thread Manuel López-Ibáñez
On 31 July 2016 at 21:54, phi gcc wrote: > Why should I ? I am not a gcc designer, just humbelly reporting a Anybody can become a GCC developer, if they want to :) > At some point one suggested reading the source, I did it real quick, > and it appears trivial that getenv("TERM") is wrongly proce

Re: diag color

2016-07-31 Thread Manuel López-Ibáñez
On 31 July 2016 at 22:59, Jonathan Wakely wrote: > On 31 July 2016 at 22:06, phi gcc wrote: >> bugzilla don't likes me, can't get in >> Ok let's forget participation then... > > We were attacked by spammers last week and had to temporarily disable > account creation. The notice you got from bu

gcc-7-20160731 is now available

2016-07-31 Thread gccadmin
Snapshot gcc-7-20160731 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20160731/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision