Re: [PATCH] Fix Immediate Values x86_64 support old gcc

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Mathieu Desnoyers <compudj@...>
Cc: H. Peter Anvin <hpa@...>, <linux-kernel@...>, Jeremy Fitzhardinge <jeremy@...>, Ingo Molnar <mingo@...>
Date: Wednesday, May 21, 2008 - 4:37 pm

Hi Mathieu

So here we introduce a global environment variable that tells
us that gcc has "BROKEN_IMMEDIATE".
I have absolutely no clue what "BROKEN_IMMEDIATE" is so I guess others
are in the same boat. Comment please!

Consider something like this (note: no negative logic involved):
export USE_IMMEDIATE := $(call cc-ifversion, -ge, 0400, $(CONFIG_IMMEDIATE))

Then the MAkefile fragment can be simplified as:

(Or find a better name than "USE_IMMEDIATE".



And now in the source we use a direct check of the GNUC version. So this is a duplicate
of GCC_BROKEN_IMMEDIATE and not sensible comments.
"I ask myself in what way is gcc broken?"
And you DO NOT fiddle with the CONFIG_* variables - this is just plain wrong.


So you need to find a better way for this.


--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] Fix Immediate Values x86_64 support old gcc, Mathieu Desnoyers, (Wed May 21, 1:01 pm)
Re: [PATCH] Fix Immediate Values x86_64 support old gcc, Sam Ravnborg, (Wed May 21, 4:37 pm)
Re: [PATCH] Fix Immediate Values x86_64 support old gcc, Mathieu Desnoyers, (Wed May 21, 5:28 pm)
Re: [PATCH] Fix Immediate Values x86_64 support old gcc, Sam Ravnborg, (Wed May 21, 5:46 pm)
Re: [PATCH] Fix Immediate Values x86_64 support old gcc (v2), Mathieu Desnoyers, (Wed May 21, 5:57 pm)
Re: [PATCH] Fix Immediate Values x86_64 support old gcc (v3), Mathieu Desnoyers, (Wed May 21, 7:24 pm)
Re: [PATCH] Fix Immediate Values x86_64 support old gcc (v3), Mathieu Desnoyers, (Wed May 21, 10:03 pm)
[PATCH ftrace.git sched-fixes.git] Fix Immediate Values x86_..., Mathieu Desnoyers, (Tue May 27, 9:12 am)