I have a question about the DRAP register (used for dynamic stack alignment)
and about reserving/using hard registers in general. I am trying to understand
where, if a drap register is allocated, GCC is told not to use it during
general register allocation. There must be some code somewhere for
Snapshot gcc-5-20150616 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20150616/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
On Mon, 15 Jun 2015, Andrew Pinski wrote:
> > results in asm redirection for log to __log_finite and final vector
> > function name becomes _ZGVbN2v___log_finite.
> >
> > With point of view from C Library side, it reflects in addition of asm
> > redirections _ZGVbN2v___log_finite = _ZGVbN2v_log in
Hi,
This is another comment on builtin/header comments. While for
alignment/size bounds there is no reason to use builtin as gcc should
also optimize header version with
if (__builtin_constant_p(n<42) && n < 42)
there is information that you could get only with gcc help. Its that
while speculati
