Snapshot gcc-4.5-20090402 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.5-20090402/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
From: "Janis Johnson"
I get the failure Richard mentioned when I use -D_FORTIFY_SOURCE=2
-fstack-protector but no failures without those options. This is on
powerpc64-linux (but defaulting to -m32) with:
RHEL 5.3
GCC 4.3.2
GMP 4.2.4
MPFR 2.4.1
MPC 0.6
Okay the -D_FORTIFY_SOURCE=2 bug has b
From: "Jakub Jelinek"
man 3p sprintf says:
If copying takes place between objects that overlap as a result of a call
to
sprintf() or snprintf(), the results are undefined.
ISO C99 7.19.6.6 has similar wording:
If copying takes place between objects that overlap, the behavior is
undefined
On Thu, Apr 02, 2009 at 01:55:29PM -0700, Kaveh R. Ghazi wrote:
> From: "Marc Glisse"
> >This could be related to a call to sprintf(str,...,str,...), which
> >according to the doc is undefined behaviour.
>
> Doc? I don't see it in the man page. Got a url?
man 3p sprintf says:
If copying take
From: "Marc Glisse"
This could be related to a call to sprintf(str,...,str,...), which
according to the doc is undefined behaviour.
Doc? I don't see it in the man page. Got a url?
> The "Compilation Process" transforms code entirely represented in
> non-intermediate languages designed for human-written code,
> and/or in Java Virtual Machine byte code, into Target Code.
Two months for this??? And what about CLR (Mono, .NET) bytecode for example???
Paolo
> With SEH you can catch that kind of errors and that's why it's so
> interesting in embedded world
That's also why SEH is a major pain for optimization. The compiler
would have to identify every instruction that may trigger an
exception, and either treat that instruction as a scheduling boundary
In order for my CSE const anchor patch to work I needed to drastically lower
the cost of immediate addition in the MIPS backend. This was acceptable as a
proof of concept but not in general of course.
The problem is with "single-insn"/simple constants. We would also like these
to use const ancho
On Thu, Apr 02, 2009 at 12:51:55PM +0200, Uros Bizjak wrote:
> I guess that somehow we have to prevent choose_reload_regs to blindly
> substitute memory_operand with register when paradoxical subregs are
> involved. The condition for the substitution should be similar to the
> condition in nonzero_
The trunk will be frozen for the merge of the alias-improvements branch
tomorrow, Friday, April 3rd starting 8am UTC. I will do a last merge
to the branch at that point, do a bootstrap & regtest cycle and
finally commit the merge to trunk.
Thanks for your cooperation.
Richard.
--
Richard Guen
On Wed, Apr 1, 2009 at 3:34 PM, Joern Rennecke wrote:
> I suggest you first find out more what is exactly reloaded and where
> the inheritance occurs - inheritance can be done by choose_reload_regs
> or later in emit_reload_insns and its subfunctions.
>
> I.e. set a breakpoint on find_reloads and
Dave Korn wrote:
> First attempt (attached) didn't go so well. When building libgcc2, I get
> an ICE in the preprocessor, here:
> As far as I can tell, CHAR16_TYPE is:
>
> (gdb) x/s 0x1fdb0f6 0x1fdb0f6 <__FUNCTION__.59453+167>: "unsigned
> short" (gdb)
>
> Is this perhaps related to the w
On Wed, 01 Apr 2009 11:22:22 -0700, Ian Lance Taylor
wrote:
> "Vincent R." writes:
>
>>> gcc will do the right thing if you put statements in an exception
>>> region.
>>
>> Hum how gcc can do that kind of things, is it some kind of voodoo ?
>> __except is not implemented yet and is more than a l
13 matches
Mail list logo
