RE: selective linking of floating point support for *printf / *scanf

2014-08-27 Thread Thomas Preud'homme
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com] > Sent: Wednesday, August 27, 2014 7:54 PM > > Well, my goal was to have the selection be automatic for most use cases. > That you can do a manual selection by providing -u / -l arguments to the > linker is pretty much a given. > Hmm, ins

gcc-4.9-20140827 is now available

2014-08-27 Thread gccadmin
Snapshot gcc-4.9-20140827 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20140827/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.9 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Re: Conditional negation elimination in tree-ssa-phiopt.c

2014-08-27 Thread Jeff Law
On 08/13/14 08:57, Richard Earnshaw wrote: The problem with the frankenmonster patterns is that they tend to proliferate into the machine description, and before you know where you are the back-end is full of them. Can't argue with that :-) I really do think that the best solution would be to

Re: Conditional negation elimination in tree-ssa-phiopt.c

2014-08-27 Thread Jeff Law
On 08/18/14 04:33, Kyrill Tkachov wrote: On 18/08/14 10:19, Richard Earnshaw wrote: On 14/08/14 09:45, Kyrill Tkachov wrote: On 13/08/14 18:32, Segher Boessenkool wrote: On Wed, Aug 13, 2014 at 03:57:31PM +0100, Richard Earnshaw wrote: The problem with the frankenmonster patterns is that the

Re: Enable EBX for x86 in 32bits PIC code

2014-08-27 Thread Jeff Law
On 08/26/14 15:42, Ilya Enkovich wrote: diff --git a/gcc/calls.c b/gcc/calls.c index 4285ec1..85dae6b 100644 --- a/gcc/calls.c +++ b/gcc/calls.c @@ -1122,6 +1122,14 @@ initialize_argument_information (int num_actuals ATTRIBUTE_UNUSED, call_expr_arg_iterator iter; tree arg; +if (

Re: Enable EBX for x86 in 32bits PIC code

2014-08-27 Thread Vladimir Makarov
On 2014-08-26 5:42 PM, Ilya Enkovich wrote: Hi, Here is a patch I tried. I apply it over revision 214215. Unfortunately I do not have a small reproducer but the problem can be easily reproduced on SPEC2000 benchmark 175.vpr. The problem is in read_arch.c:701 where float value is compared w

consistent naming of passes....

2014-08-27 Thread Basile Starynkevitch
Hello all, When I compile some file (precisely, the gcc/melt-runtime.cc from the latest melt branch) with -O1 -fdump-passes (using GCC 4.9) I'm getting notably ipa-cp : OFF ipa-cdtor : OFF ipa-inlin

Register allocation: caller-save vs spilling

2014-08-27 Thread Wilco Dijkstra
Hi, I'm investigating various register allocation inefficiencies. The first thing that stands out is that GCC both supports caller-saves as well as spilling. Spilling seems to spill all definitions and all uses of a liverange. This means you often end up with multiple reloads close together, wh

Re: Possible LRA issue?

2014-08-27 Thread Daniel Gutson
On Wed, Aug 27, 2014 at 12:16 PM, Ajit Kumar Agarwal wrote: > The cause of xmalloc occurring at times given below in Register Allocator > will not be caused only by the structure and changing the passed S as > template argument. > It depends on how the below structures is referenced or used. Fro

RE: Possible LRA issue?

2014-08-27 Thread Ajit Kumar Agarwal
The cause of xmalloc occurring at times given below in Register Allocator will not be caused only by the structure and changing the passed S as template argument. It depends on how the below structures is referenced or used. From the stack trace I can see the live ranges creation is based on how

Possible LRA issue?

2014-08-27 Thread Daniel Gutson
Hi, I have a large codebase where at some point, there's a structure that takes an unsigned integer template argument, and uses as the size of an array, something like template struct Struct { typedef std::array Chunk; typedef std::list Content; Content c; }; Changing the values

Re: selective linking of floating point support for *printf / *scanf

2014-08-27 Thread Joern Rennecke
On 27 August 2014 11:41, Thomas Preud'homme wrote: >> From: Joern Rennecke [mailto:joern.renne...@embecosm.com] >> Sent: Wednesday, August 27, 2014 6:13 PM >> >> I don't see how it can be any other way. We want to be able to compile >> translation units individually, and then let the linker sort

RE: selective linking of floating point support for *printf / *scanf

2014-08-27 Thread Thomas Preud'homme
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com] > Sent: Wednesday, August 27, 2014 6:13 PM > > I don't see how it can be any other way. We want to be able to compile > translation units individually, and then let the linker sort out if we need > the > floating point enabled implement

Re: Turning a single warning into an error in dejagnu test

2014-08-27 Thread Marek Polacek
On Wed, Aug 27, 2014 at 10:59:40AM +0100, Dominik Vogt wrote: > I'm writing a dejagnu test and encounter this warning at one place: > > warning: passing argument 1 of '...' makes integer from pointer > without a cast [enabled by default] > > Now, I have a "{ dg-error ... }" comment in that li

Re: selective linking of floating point support for *printf / *scanf

2014-08-27 Thread Joern Rennecke
On 27 August 2014 08:02, Thomas Preud'homme wrote: >> From: Joern Rennecke [mailto:joern.renne...@embecosm.com] >> Sent: Tuesday, August 26, 2014 6:44 PM >> >> Due to the library order defined in the specs, the float-enbled printf >> definition will >> be picked up from libprintf_flt.a . > > It se

Turning a single warning into an error in dejagnu test

2014-08-27 Thread Dominik Vogt
I'm writing a dejagnu test and encounter this warning at one place: warning: passing argument 1 of '...' makes integer from pointer without a cast [enabled by default] Now, I have a "{ dg-error ... }" comment in that line. The line is generated from a script among hundreds of others that are

RE: selective linking of floating point support for *printf / *scanf

2014-08-27 Thread Thomas Preud'homme
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com] > Sent: Tuesday, August 26, 2014 6:44 PM > > Due to the library order defined in the specs, the float-enbled printf > definition will > be picked up from libprintf_flt.a . It seems to me that it relies heavily on how symbol resolution wo