[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

--- Comment #7 from thunderwolf66102 at yahoo dot com 2010-02-01 08:49 --- Under Gentoo, GCC x86_64-pc-linux-gnu-4.4.2 appears to also build a broken glibc 2.9. I have tried many times over the past several days to build and install gentoo's 2.9_p20081201-r3 to replace a previous 2.9_p

[Bug fortran/42309] [4.3/4.4/4.5 Regression] Problem with a pointer array passed to a subroutine

-- burnus at gcc dot gnu dot org changed: What|Removed |Added GCC host triplet|4.5.0 | Keywords||wrong-code Know

[Bug fortran/42900] gfortran.dg/stat_[12].f90 may fail on NFS filesystems

--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld dot DE 2010-02-01 09:21 --- Subject: Re: gfortran.dg/stat_[12].f90 may fail on NFS filesystems > --- Comment #1 from rguenth at gcc dot gnu dot org 2010-01-29 22:35 > --- > I'd say add a comment to the testcase and WONTFIX.

[Bug middle-end/42919] [4.3/4.4/4.5 Regression] Argument unnecessarily spilled

--- Comment #6 from rguenther at suse dot de 2010-02-01 09:23 --- Subject: Re: [4.3/4.4/4.5 Regression] Argument unnecessarily spilled On Mon, 1 Feb 2010, matz at gcc dot gnu dot org wrote: > --- Comment #4 from matz at gcc dot gnu dot org 2010-02-01 02:41 --- > Well, actual

[Bug middle-end/39193] Internal compiler error during FreeBSD 7.1 kernel compilation

--- Comment #15 from rguenth at gcc dot gnu dot org 2010-02-01 10:14 --- GCC 4.2.x is no longer supported. FreeBSD is on its own. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added -

[Bug c/42907] -fstrict-aliasing breaks valid code

--- Comment #29 from emn13+gcc at nerbonne dot org 2010-02-01 10:16 --- What's particularly unfortunate about this instance is the fact that gcc fails to warn you about the erroneous code, despite the obvious signs and despite -Wall. Line 15 is obviously potentially problematic, but it

[Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8

--- Comment #8 from mikpe at it dot uu dot se 2010-02-01 11:13 --- There are known aliasing bugs in older glibc releases that result in broken code when compiled with gcc-4.4. The fix is to update glibc or to patch it. See . -- http:/

[Bug middle-end/39193] Internal compiler error during FreeBSD 7.1 kernel compilation

--- Comment #16 from steven at gcc dot gnu dot org 2010-02-01 11:32 --- On a not-completely-OT note: Can anyone explain what this WITHOUT_GPLV3 is about? I can't find any mentioning of it on freebsd.org... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39193

[Bug middle-end/42919] [4.3/4.4/4.5 Regression] Argument unnecessarily spilled

--- Comment #7 from matz at gcc dot gnu dot org 2010-02-01 11:53 --- Or making STRICT_ALIGNMENT depend on the type or mode. So that e.g. "!align(8) && align(4) && !STRICT_ALIGN(long long)" would be acceptable, but "!align(16) && STRICT_ALIGN(m128d)" would not. Or making it depend on th

[Bug c/42907] -fstrict-aliasing breaks valid code

--- Comment #30 from matz at gcc dot gnu dot org 2010-02-01 12:24 --- See comment #3 for how (newer) GCC does warn at line 15. Not with the default options, though, but this has good reasons (too many false positives). You are right that we should be able to improve our diagnostics in

[Bug c/42907] -fstrict-aliasing breaks valid code

--- Comment #31 from fejj at novell dot com 2010-02-01 13:08 --- Michael: I know that tail->value = is clearly going to evil things (if done before assigning one of the nodes to tail) because only the first sizeof(void*) bytes are valid memory addresses. However, if you read the code I

[Bug c/42907] -fstrict-aliasing breaks valid code

--- Comment #32 from emn13+gcc at nerbonne dot org 2010-02-01 13:24 --- I realize that you *can* enable a specific warning that might solve this; but that's a pretty unsatisfactory state of affairs. The point is that if you've old (or external) C code *anywhere* in your app which breaks

[Bug libgomp/29986] testsuite failures

--- Comment #10 from ro at gcc dot gnu dot org 2010-02-01 13:35 --- Subject: Bug 29986 Author: ro Date: Mon Feb 1 13:35:10 2010 New Revision: 156427 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156427 Log: PR libgomp/29986 * doc/install.texi (Specific): Add sp

[Bug libgomp/29986] testsuite failures

--- Comment #11 from ro at gcc dot gnu dot org 2010-02-01 13:36 --- Fixed for 4.5.0. -- ro at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

[Bug fortran/42922] New: Wrongly rejected derived types with default initializers in PURE procedures 2

This is a problem very similar to this one: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42008 gfortran rejects the attached code because: gfortran -c err.f90 err.f90:6.20: integer :: i = 0 1 Error: Initialization of variable at (1) is not allowed in a PURE procedure How

[Bug middle-end/39193] Internal compiler error during FreeBSD 7.1 kernel compilation

--- Comment #17 from kargl at gcc dot gnu dot org 2010-02-01 15:07 --- (In reply to comment #16) > On a not-completely-OT note: Can anyone explain what this WITHOUT_GPLV3 is > about? I can't find any mentioning of it on freebsd.org... > It hasn't been implemented, yet. I don't want to

[Bug target/42671] Thumb2 generate more instructions than Thumb1 to load GOT address

--- Comment #2 from rearnsha at gcc dot gnu dot org 2010-02-01 15:34 --- Fixed in trunk with http://gcc.gnu.org/ml/gcc-patches/2010-01/msg01403.html -- rearnsha at gcc dot gnu dot org changed: What|Removed |Added --

[Bug target/42671] Thumb2 generate more instructions than Thumb1 to load GOT address

-- rearnsha at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.5.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42671

[Bug fortran/41507] Documentation misleading on MAXLOC/MINLOC array type requirement

--- Comment #4 from burnus at gcc dot gnu dot org 2010-02-01 15:41 --- PING - Are you still working on this for 4.5? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41507

[Bug c/42923] New: ice: verify_stmts failed

pc-linux-gnu Configured with: ../configure --with-libelf=/usr/local --enable-lto --prefix=/home/regehr/z/tmp/gcc-r156428-install --program-prefix=r156428- --enable-languages=c,c++ Thread model: posix gcc version 4.5.0 20100201 (experimental) (GCC) -- Summary: ice: verify_stmts fa

[Bug libstdc++/42408] Missing templatized seed()

--- Comment #2 from paolo dot carlini at oracle dot com 2010-02-01 16:20 --- Let's minimally fix this for 4.5.0, we have a (still confidential) draft of the de-conceptualized specifications. -- paolo dot carlini at oracle dot com changed: What|Removed

[Bug libstdc++/42408] Missing templatized seed()

-- paolo dot carlini at oracle dot com changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |paolo dot carlini at oracle |dot org

[Bug target/42841] [4.3/4.4/4.5 Regression] SH: Assembler complains pcrel too far.

--- Comment #26 from chrbr at gcc dot gnu dot org 2010-02-01 16:30 --- I'm afraid the unaligned access sigbug regression is another latent bug just exhibited by the fix for the original PR :-( what happens is the the GOT loading sequence is broken by a constant pool: we end up to emit:

[Bug fortran/41507] Documentation misleading on MAXLOC/MINLOC array type requirement

--- Comment #5 from domob at gcc dot gnu dot org 2010-02-01 16:30 --- Yes, in theory... But now I have holidays (since in some sense this evening) I'll get on hopefully soon so it will be well in 4.5. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41507

[Bug target/42924] New: pex-unix.c:589:1: internal compiler error: output_operand

guages=c,c++,objc,obj-c++,fortran Thread model: posix gcc version 4.5.0 20100201 (experimental) [trunk revision 156423] (GCC) -- Summary: pex-unix.c:589:1: internal compiler error: output_operand Product: gcc Version: 4.5.0 Status: U

[Bug fortran/42922] Wrongly rejected derived types with default initializers in PURE procedures 2

--- Comment #1 from burnus at gcc dot gnu dot org 2010-02-01 16:37 --- Thanks for the report! The bug is no regression and indeed the analogue to PR 42008 works also here: Index: gcc/fortran/decl.c === --- gcc/fortran/decl.

[Bug libstdc++/42925] New: Not possible to compare unique_ptr with 0

Compiling the attached C++0x program fails on 4.5 but is successful in 4.4. I think the root cause is the missing nullptr support but that doesn't make it any more useful for 4.5. -- Summary: Not possible to compare unique_ptr with 0 Product: gcc Version: 4.5.0

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #1 from gcc at magfr dot user dot lysator dot liu dot se 2010-02-01 16:47 --- Created an attachment (id=19774) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19774&action=view) Test case demonstrating the problem. compile with g++ -std=c++0x -c test.cpp to demonstrat

[Bug c++/42926] New: g++: Internal error

HI, I have tried to build Webkit on a BeagleBoard and I have a g++ internal error. I am running Ubuntu Karmic 9.10 and I am taking the source from the svn repo. To build it I am using the command $./WebKitTools/Scripts/build-webkit --qt --debug Here are some other informations: I attached the la

[Bug c++/42926] g++: Internal error

--- Comment #1 from fabien dot royer at arm dot com 2010-02-01 17:01 --- Created an attachment (id=19775) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19775&action=view) this is part of the log of the build command. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42926

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #2 from jwakely dot gcc at gmail dot com 2010-02-01 17:01 --- I think the code is invalid. In 4.4 the expression (ptr != 0) converted ptr to an unspecified-bool-type and compared that to 0. In 4.5 the impicit conversion has been removed, and you need to say static_cast(ptr)

[Bug c++/42926] g++: Internal error

--- Comment #2 from rguenth at gcc dot gnu dot org 2010-02-01 17:02 --- You ran out of memory. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/42924] [4.5 Regression] pex-unix.c:589:1: internal compiler error: output_operand

--- Comment #1 from rguenth at gcc dot gnu dot org 2010-02-01 17:03 --- I suppose it worked at some point. Please attach preprocessed source. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added --

[Bug c/42907] -fstrict-aliasing breaks valid code

--- Comment #33 from rguenth at gcc dot gnu dot org 2010-02-01 17:04 --- (In reply to comment #32) > I realize that you *can* enable a specific warning that might solve this; but > that's a pretty unsatisfactory state of affairs. > > The point is that if you've old (or external) C code

[Bug c/42923] ice: verify_stmts failed

--- Comment #1 from rguenth at gcc dot gnu dot org 2010-02-01 17:05 --- Related to or dup of PR42749. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Bugs

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #3 from gcc at magfr dot user dot lysator dot liu dot se 2010-02-01 17:19 --- I think the code is valid. The unique_ptr(nullptr_t) constructor should take the 0 and build an empty unique_ptr object that is compared with ptr. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?i

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #4 from jwakely dot gcc at gmail dot com 2010-02-01 17:22 --- there is this comparison function: template bool operator!=(const unique_ptr& x, const unique_ptr& y); What should T2 and D2 be deduced as, in the conversion from nullptr_t to unique_ptr ? Or to put it another

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #5 from paolo dot carlini at oracle dot com 2010-02-01 17:25 --- Jon, is there a thread on the reflector about related issues? I spotted something but couldn't exactly remember... Anyway, just want to add that I do not see why the C++ front-end, for some reason, decides to

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #6 from jwakely dot gcc at gmail dot com 2010-02-01 17:36 --- (In reply to comment #5) > Jon, is there a thread on the reflector about related issues? I spotted > something but couldn't exactly remember... LWG 834 is about comparing unique_ptr::pointer to nullptr_t LWG 130

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #7 from paolo dot carlini at oracle dot com 2010-02-01 17:38 --- Ok, agreed... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42925

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #8 from paolo dot carlini at oracle dot com 2010-02-01 17:39 --- Let's keep this open for one sec, in case Jason believes that list of candidates could be actually made less confusing to the user. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42925

[Bug target/42924] [4.5 Regression] pex-unix.c:589:1: internal compiler error: output_operand

--- Comment #2 from dave at hiauly1 dot hia dot nrc dot ca 2010-02-01 18:08 --- Subject: Re: [4.5 Regression] pex-unix.c:589:1: internal compiler error: output_operand > I suppose it worked at some point. Please attach preprocessed source. Yes, it worked a few days ago. Att

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #9 from jason at gcc dot gnu dot org 2010-02-01 19:31 --- It does seem like it would be helpful to include templates in the list of all candidates. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42925

[Bug c/42927] New: type mismatch in shift expression produces ice with -O3

I just tried to compile the package scsires-0.7-4.7 with the GNU C compiler version 4.5 snapshot 20100128 and the compiler said scsires.c: In function 'scsires_issue_reservation': scsires.c:911:1: error: type mismatch in shift expression vector unsigned int vector int vect_var_.289_442 = vect_per

[Bug c/42927] type mismatch in shift expression produces ice with -O3

--- Comment #1 from dcb314 at hotmail dot com 2010-02-01 19:39 --- Created an attachment (id=19777) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19777&action=view) C source code -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42927

[Bug tree-optimization/42927] [4.5 Regression] type mismatch in shift expression produces ice with -O3

-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Component|c |tree-optimization GCC host triplet|x86_64-suse-linux | G

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #10 from paolo dot carlini at oracle dot com 2010-02-01 19:40 --- I see. In principle I think the user would like to see only operator!=(int, int) and indeed: template bool operator!=(const unique_ptr<_Tp, _Tp_Deleter>&, const unique_ptr<_Up, _

[Bug libstdc++/42408] Missing templatized seed()

--- Comment #3 from paolo at gcc dot gnu dot org 2010-02-01 19:45 --- Subject: Bug 42408 Author: paolo Date: Mon Feb 1 19:45:23 2010 New Revision: 156430 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156430 Log: 2010-02-01 Paolo Carlini PR libstdc++/42408 *

[Bug libstdc++/42408] Missing templatized seed()

--- Comment #4 from paolo dot carlini at oracle dot com 2010-02-01 19:48 --- Done. -- paolo dot carlini at oracle dot com changed: What|Removed |Added Status

[Bug target/41399] [4.5 Regression] Scheduler gives huge dependence graph compiling fortran/intrinsic.c on ARM

--- Comment #23 from vmakarov at gcc dot gnu dot org 2010-02-01 19:52 --- Subject: Bug 41399 Author: vmakarov Date: Mon Feb 1 19:52:42 2010 New Revision: 156431 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156431 Log: 2010-02-01 Vladimir Makarov PR target/41399

[Bug lto/42928] New: crash when compiling scummvm on Ubuntu 9.10/amd64 with -flto and -fuse-linker-plugin

with trunk revision 156392 1. get and unpack the scummvm src: http://helllabs.org/scummvm/scummvm-20100201.tar.bz2 2. ./configure --enable-all-engines 3. edit config.mk so that CXXFLAGS reads as "-O2 -Wall -Wextra -g -ansi -W -Wno-unused-parameter -Wno-empty-body -pedantic -flto&quo

[Bug c++/42929] New: ICE when compiling PPL

The error occurs when compiling PPL with GCC 4.5.0 revision 156383 -- Summary: ICE when compiling PPL Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassig

[Bug c++/42929] ICE when compiling PPL

--- Comment #1 from denis dot onischenko at gmail dot com 2010-02-01 20:28 --- Created an attachment (id=19778) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19778&action=view) preprocessed source -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42929

[Bug c++/42929] ICE when compiling PPL

--- Comment #2 from denis dot onischenko at gmail dot com 2010-02-01 20:28 --- Created an attachment (id=19779) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19779&action=view) console output -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42929

[Bug c++/42929] [4.5 Regression] ICE when compiling PPL

--- Comment #3 from pinskia at gcc dot gnu dot org 2010-02-01 20:30 --- I think this is a dup of bug 42915. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/42924] [4.5 Regression] pex-unix.c:589:1: internal compiler error: output_operand

--- Comment #4 from dave at hiauly1 dot hia dot nrc dot ca 2010-02-01 21:00 --- Subject: Re: New: pex-unix.c:589:1: internal compiler error: output_operand Breakpoint 3, output_addr_const (file=0x83fffdfd0020, x=0x83fffdc75228) at ../../gcc/gcc/final.c:3521 3521

[Bug middle-end/42930] New: crash when compiling scummvm on Ubuntu 9.10/amd64 with

with trunk revision 156392 1. get and unpack the scummvm src: http://helllabs.org/scummvm/scummvm-20100201.tar.bz2 2. ./configure --enable-all-engines 3. edit config.mk so that CXXFLAGS := -O2 -funswitch-loops -ftree-loop-linear -floop-interchange -floop-strip-mine -floop-block -ftree-loop

[Bug tree-optimization/42931] New: -ftree-loop-linear - valgrind warns about using uninitialized variable

Command line: valgrind --trace-children=yes gcc -O1 -ftree-loop-linear -c testcase.c Tested revisions: trunk r156367 - fail trunk r155363 - fail trunk r153685 - fail 4.4 r156256 - fail 4.4 r155966 - fail 4.4 r155463 - fail 4.4 r155365 - fail 4.4 r154975 - fail 4.4 r153668 - OK 4.4 r149995 - OK 4.4

[Bug tree-optimization/42931] -ftree-loop-linear - valgrind warns about using uninitialized variable

--- Comment #1 from zsojka at seznam dot cz 2010-02-01 21:27 --- Created an attachment (id=19780) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19780&action=view) original, unreduced testcase (from jpeg sources) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42931

[Bug fortran/42922] Wrongly rejected derived types with default initializers in PURE procedures 2

--- Comment #2 from burnus at gcc dot gnu dot org 2010-02-01 21:38 --- Subject: Bug 42922 Author: burnus Date: Mon Feb 1 21:37:49 2010 New Revision: 156433 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156433 Log: 2010-02-01 Tobias Burnus PR fortran/42922 *

[Bug fortran/42922] Wrongly rejected derived types with default initializers in PURE procedures 2

--- Comment #3 from burnus at gcc dot gnu dot org 2010-02-01 21:38 --- FIXED on the trunk (4.5). Thanks for the report! -- burnus at gcc dot gnu dot org changed: What|Removed |Added --

[Bug libstdc++/42847] [4.5 Regression] failure while configuring libstdc++

--- Comment #5 from rainer at emrich-ebersheim dot de 2010-02-01 21:46 --- (In reply to comment #3) > I haven't tried a whole lot of cross compiler building. There's no reference > to cygwin anywhere in crossconfig.m4, so perhaps we need --with-newlib? > Sorry guys, my fault. Indeed

[Bug target/42920] gcc does not produce necessary vec_lvrx instructions

--- Comment #7 from pinskia at gcc dot gnu dot org 2010-02-01 21:54 --- > if it ain't in Ubuntu > repos anymore, I can't remember how to build these things. :) Well it works in 4.4.0 so closing as invalid as the support for these intrinsics were not added until 4.4 and they were fixed be

[Bug bootstrap/42932] New: unknown endianness, Solaris 10 SPARC

% export PATH=/cairo/tmp/jblaine:/usr/sfw/bin:/usr/ccs/bin:/usr/bin:/bin:/sbin:/usr/sbin # # Note /cairo/tmp/jblaine is in PATH for GNU find per bug # 38715. Everything else in the PATH is standard Solaris 10 SPARC. # % uname -a SunOS cairo 5.10 Generic_13-08 sun4u sparc SUNW,Sun-Fire-280R %

[Bug target/41399] [4.5 Regression] Scheduler gives huge dependence graph compiling fortran/intrinsic.c on ARM

--- Comment #24 from steven at gcc dot gnu dot org 2010-02-01 22:13 --- . -- steven at gcc dot gnu dot org changed: What|Removed |Added Status|NEW

[Bug fortran/42650] F90: DT function with in-line DT definition and RESULT is rejected

--- Comment #2 from burnus at gcc dot gnu dot org 2010-02-01 22:16 --- The problem is somehow that for the second parsing using decl.c's gfc_match_decl_type_spec one has in: else if (ts->kind == -1) { int iface = gfc_state_stack->previous->state != COMP_INTERFACE

[Bug middle-end/42930] crash when compiling scummvm on Ubuntu 9.10/amd64 with -floop-block

--- Comment #1 from matt at use dot net 2010-02-01 22:24 --- I have narrowed it to the following commandline (-O1 -floop-block): ~/src/scummvm$ /home/matt/bin/g++ -Wp,-MMD,"engines/cine/.deps/gfx.d",-MQ,"engines/cine/gfx.o",-MP -Wall -O1 -floop-block -ansi -fcheck-new -DSCUMMVM_SVN_REVIS

[Bug middle-end/42930] crash when compiling scummvm on Ubuntu 9.10/amd64 with -floop-block

--- Comment #2 from matt at use dot net 2010-02-01 22:25 --- Created an attachment (id=19781) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19781&action=view) pre-processed source file that causes the crash -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42930

[Bug fortran/42650] F90: DT function with in-line DT definition and RESULT is rejected

--- Comment #3 from burnus at gcc dot gnu dot org 2010-02-01 22:46 --- Patch: Index: gcc/fortran/parse.c === --- gcc/fortran/parse.c (Revision 156433) +++ gcc/fortran/parse.c @@ -111,7 +111,7 @@ decode_specification_state

[Bug ada/42554] Can't build gnatlink, gnatmake

--- Comment #5 from simon at pushface dot org 2010-02-01 22:53 --- I think this bug is caused by a much more fundamental problem: the -c switch to ranlib, which seems to be a Darwin special, appears to cause this problem (at any rate with Xcode >= 3.2, ie darwin10. The top-level configu

[Bug ada/42554] Can't build gnatlink, gnatmake

--- Comment #6 from simon at pushface dot org 2010-02-01 22:55 --- Created an attachment (id=19782) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19782&action=view) Patch to configure.ac, configure -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42554

[Bug tree-optimization/42931] -ftree-loop-linear - valgrind warns about using uninitialized variable

--- Comment #2 from zsojka at seznam dot cz 2010-02-01 23:27 --- Created an attachment (id=19783) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19783&action=view) reduced testcase The computed value isn't used anyway, so this problem shouldn't affect generated code. -- http:/

[Bug testsuite/42933] New: Test suite reports excess unexpected failures when using RUNTESTFLAGS to pass extra options

While investigating configuration-dependent behavior in GCC, I ran the test suite twice as shown below. In the first case, RUNTESTFLAGS passes no extra flags, and the summary shows 13 unexpected failures. In the second case I send a great many options and get 188 unexpected failures. I am willin

[Bug libstdc++/42925] Not possible to compare unique_ptr with 0

--- Comment #11 from paolo dot carlini at oracle dot com 2010-02-02 01:04 --- Ok, I guess we can close this. -- paolo dot carlini at oracle dot com changed: What|Removed |Added --

[Bug testsuite/42933] Test suite reports excess unexpected failures when using RUNTESTFLAGS to pass extra options

--- Comment #1 from pinskia at gcc dot gnu dot org 2010-02-02 01:14 --- Well RUNTESTFLAGS is really only useful for options which change the ABI and have a multilib. Like -fPIC/-m64/-m32, etc. -std=c++0x changes the input language which is used so therefor changes the whole testsuite.

[Bug testsuite/42933] Test suite reports excess unexpected failures when using RUNTESTFLAGS to pass extra options

--- Comment #2 from bgarvin at acm dot org 2010-02-02 01:30 --- (In reply to comment #1) > Well RUNTESTFLAGS is really only useful for options which change the ABI and > have a multilib. Like -fPIC/-m64/-m32, etc. -std=c++0x changes the input > language which is used so therefor change

[Bug testsuite/42933] Test suite reports excess unexpected failures when using RUNTESTFLAGS to pass extra options

--- Comment #3 from pinskia at gcc dot gnu dot org 2010-02-02 01:36 --- >torture For the torture test you can set the TORTURE OPTIONS separately and let the testsuite do the rest. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42933

[Bug testsuite/42933] Test suite reports excess unexpected failures when using RUNTESTFLAGS to pass extra options

--- Comment #4 from bgarvin at acm dot org 2010-02-02 01:43 --- (In reply to comment #3) > >torture > For the torture test you can set the TORTURE OPTIONS separately and let the > testsuite do the rest. > Yeah, that's what I meant. Thanks for the clarification and sorry about the inva

[Bug ada/42554] Can't build gnatlink, gnatmake

--- Comment #7 from howarth at nitro dot med dot uc dot edu 2010-02-02 01:55 --- Why not remove the duplicate linkage of s-secsta.o in gnatlink and gnatmake? There is no reason to link it in a second time since it is already in libgnat.a. -- http://gcc.gnu.org/bugzilla/show_bug.cgi

[Bug fortran/42309] Problem with a pointer array passed to a subroutine

--- Comment #3 from pault at gcc dot gnu dot org 2010-02-02 05:17 --- I am not at all happy with designating this bug a regression. This worked with 4.1 and 4.2 because the stride measure for the derived type was the same as an integer; add more components and see what happens I am

[Bug ada/42554] Can't build GNAT tools

--- Comment #8 from simon at pushface dot org 2010-02-02 06:26 --- It's much worse than that.. Aside from the other object file which triggers the same bug, the make of gnatlink and gnatmake calls in libgnat.a twice. And when you build the other GNAT tools, it calls in all the Ada-deri