If it is possible, I would like to begin with a small project to get
familiar with GCC code. I have been through the "Simple GCC projects"
web page and I would be interested in project such as "Convert
reorg.c to use the flow graph".
Could someone help me to get involved ?
I cannot but reinfo
Richard Sandiford wrote:
Uros Bizjak <[EMAIL PROTECTED]> writes:
Forwarded is a short discussion with Mr. de Dinechin (forwarded with
permission), where the possibility to import crlibm as the default gcc
math library is discussed. I would like to ask members of the GCC SC for
the opinion o
Hello!
It is currently unclear whether GNU/Hurd, GNU/k*BSD, or GNU/* in general
should share stuff (like configuration branches inside `config.gcc',
files from `config/') with GNU/Linux. This is -- because of the targets
being pretty much similar -- how it used to be done in the past. But now
GC
Thomas Schwinge, le Sun 11 Nov 2007 15:58:08 +0100, a écrit :
> To state this intended similarity clearly, one could rename, e.g.,
> `config/linux.h' to `config/gnu-shared.h' and then have a new (nearly
> empty) file `config/linux.h' additionally to the existing `config/gnu.h',
> `config/kfreebsd-g
On Sun, 11 Nov 2007, Thomas Schwinge wrote:
> To give an example: all the GNU/* configurations use the `config/linux.h'
> file, even though only one of the possible GNU/* configurations is
GNU/Linux for Alpha, Power and SPARC don't use the shared file, so in
those cases config/$cpu/linux.h has t
On Sun, Nov 11, 2007 at 11:05:43AM +0100, Uros Bizjak wrote:
> Richard Sandiford wrote:
> >Uros Bizjak <[EMAIL PROTECTED]> writes:
> >
> >>Forwarded is a short discussion with Mr. de Dinechin (forwarded with
> >>permission), where the possibility to import crlibm as the default gcc
> >>math lib
Alexandre Oliva wrote:
> 1. introduce, early in compilation (when entering SSA), annotations
> that map user-level variables whose location may vary throughout their
> lifetime to implementation-level variables or expressions at every
> point of assignment and PHI joins.
>
> 2. keep those annotat
Robert Dewar wrote:
> Ian Lance Taylor wrote:
>> Alexandre Oliva <[EMAIL PROTECTED]> writes:
>>
>>> So... The compiler is outputting code that tells other tools where to
>>> look for certain variables at run time, but it's putting incorrect
>>> information there. How can you possibly argue that t
