Quoting Joern Rennecke :
Does that mean you acknowledge that we shouldn't have CUMULATIVE_ARGS
taking hooks in the global target vector?
FWIW, I think the attached patch would be approximately what it takes to
remove the CUMULATIVE_ARGS taking hooks from the global target vector
and put them i
Hi,
I have just faced a problem where a C++ program (which I get in binary
form - I can't recompile) crashes when it uses libstdc++.so.6 from
GCC-4.5.1, while it works when using libstdc++.so.6 from GCC-4.4.5.
I am using an x86 machine.
Are there any known incompatibilities between these two lib
On Tue, Nov 16, 2010 at 10:22:00PM -0500, Joern Rennecke wrote:
> Quoting Nathan Froyd :
> >I am admittedly a C++ newbie; the first thing I thought of was:
> >
> >class gcc::cumulative_args {
> > virtual void advance (...) = 0;
> > virtual rtx arg (...) = 0;
> > virtual rtx incoming_arg (...) {
Quoting Nathan Froyd :
On Tue, Nov 16, 2010 at 10:22:00PM -0500, Joern Rennecke wrote:
...
Does that mean you acknowledge that we shouldn't have CUMULATIVE_ARGS
taking hooks in the global target vector?
Maybe? I think the methods discussed in this thread would be better for
when we do move
Christophe Lyon writes:
> I have just faced a problem where a C++ program (which I get in binary
> form - I can't recompile) crashes when it uses libstdc++.so.6 from
> GCC-4.5.1, while it works when using libstdc++.so.6 from GCC-4.4.5.
>
> I am using an x86 machine.
>
> Are there any known incomp
Hi.
My build this morning failed when libquadmath was being built. Things
failed when configuring in the 'amd64' subdirectory - the bits below
are taken from the 'config.log' in that directory:
configure:3040: /export/home/arth/gnu/gcc-1117/./gcc/xgcc
-B/export/home/arth/gnu/gcc-1117/./gcc/
-B/
Art Haas wrote:
My build this morning failed when libquadmath was being built. Things
failed when configuring in the 'amd64' subdirectory - the bits below
are taken from the 'config.log' in that directory:
There are two known problems:
a) libquadmath should - at least for now - only be build b
* Tobias Burnus wrote on Wed, Nov 17, 2010 at 08:20:39PM CET:
> b) Building with a cross compiler is not supported by the
> libquadmath configure script
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46520
You should probably try out GCC_NO_EXECUTABLES in configure.ac
and check with a couple of cr
Trying to bootstrap rev. 166873, on Cygwin, configuring with:
/tmp/gcc-4.6-r166873/configure --prefix=/usr/local/gfortran
--program-suffix=-4.6 --enable-languages=c,c++,fortran
--enable-checking=release --enable-threads=posix --enable-libgomp
--disable-bootstrap --disable-libmudflap --disable-
Why does everyone think that I and Fortran have something to do with it
if something breaks?* ;-)
The issue is known and a fix, which seemingly works on Darwin, exists.
See: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46510
Angelo Graziosi wrote:
/tmp/gcc-4.6-r166873/libgomp/barrier.c:41:1: int
Ralf Wildenhues writes:
> * Tobias Burnus wrote on Wed, Nov 17, 2010 at 08:20:39PM CET:
>> b) Building with a cross compiler is not supported by the
>> libquadmath configure script
>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46520
>
> You should probably try out GCC_NO_EXECUTABLES in configu
Rainer Orth writes:
> I won't post a proper patch until it has completed, just a heads-up to
> those running into the same failures.
While the build completed with the patch I've posted, fortran testing
for the non-default multilib is completely broken, e.g.
Setting LD_LIBRARY_PATH to
.:/var/g
Rainer Orth wrote:
While the build completed with the patch I've posted, fortran testing
for the non-default multilib is completely broken, e.g.
That's in a way the a duplicate of PR 46516. Or at least the solution is
similar: Getting rid of libgfortran.spec and fall back (again) to having
th
Ralf Wildenhues writes:
> I casually looked at libgo/{Makefile.am,configure.ac}.
Thanks for the review.
> You don't need to list .c files in the BUILT_SOURCES variable if they
> are also listed in some _SOURCES variable (and are not
> undocumented prerequisites for other targets). make will k
Hi Axel,
Axel Freyn escribió:
[CUT]
> I simply added debug output before/after each "event"
> My gcc-generated executable says the following at runtime:
> main 1
> type_schema called the 1 time
> type_schema 1
> Contructor called the 1 time
> Constructor sponge_object_schema: 1
> type_schema c
[This question should have been sent to gcc-help, this list is for
discussing development of GCC]
On 18 November 2010 03:03, Gilberto Cuba Ricardo wrote:
>
> Maybe it's possible, though, I searched in the working draft of
> standard programming c++ of this year that: "Static initialization shall
>
* Rainer Orth wrote on Wed, Nov 17, 2010 at 09:15:55PM CET:
>
> * One cannot -lm to libquadmath_la_LIBADD since that gets passed to nm,
> which doesn't know (and doesn't need to be run) -lm.
That's a bug in the rule using nm then, though.
> Again, as in
> libjava/Makefile.am, I've moved it
Some text size measurement.
Summary:
1) LTO with -O3 bloats up code considerably;
2) LTO with -O2 reduces text size compared with -O2
3) Google 4.4.3 based compiler is really effective in reducing C++
program size -- this is where the focus of the tuning was done.
Witnessed by eon in SPEC2k and al
18 matches
Mail list logo
