[Bug libstdc++/41861] New: does not use monotonic_clock

2009-10-28 Thread atgraham at gmail dot com
bstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: atgraham at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41861

[Bug libstdc++/33896] New: std::tr1::array has too-conservative alignment on _M_instance

2007-10-25 Thread atgraham at gmail dot com
ve alignment on _M_instance Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: atgraham at gmail

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-10-02 Thread atgraham at gmail dot com
--- Comment #9 from atgraham at gmail dot com 2007-10-03 05:31 --- The patch from Richard appears to fix the problem. With his patch applied, the compiler output is correct. -- atgraham at gmail dot com changed: What|Removed |Added

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-08-24 Thread atgraham at gmail dot com
--- Comment #7 from atgraham at gmail dot com 2007-08-24 16:34 --- binutils bug created: http://sourceware.org/bugzilla/show_bug.cgi?id=4959 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33169

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-08-24 Thread atgraham at gmail dot com
--- Comment #5 from atgraham at gmail dot com 2007-08-24 16:12 --- Created an attachment (id=14104) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14104&action=view) Output of "mipsel-linux-gcc -Os -s tworelocs.c" gcc output attached. -- http://gcc

[Bug target/33169] Compiler generates two different relocs for the same symbol

2007-08-24 Thread atgraham at gmail dot com
--- Comment #3 from atgraham at gmail dot com 2007-08-24 16:00 --- Here is a smaller bit of code for reproducing this problem. This doesn't depend on any C++. #include "pthread.h" static __typeof(pthread_mutex_lock) __gthrw_pthread_mutex_lock __attribute_

[Bug c++/33169] Compiler generates two different relocs for the same symbol

2007-08-23 Thread atgraham at gmail dot com
--- Comment #1 from atgraham at gmail dot com 2007-08-24 00:40 --- This problem is due to the fact that GTHREAD_USE_WEAK is incorrectly defined for this architecture. -- atgraham at gmail dot com changed: What|Removed |Added

[Bug c++/33169] New: Compiler generates two different relocs for the same symbol

2007-08-23 Thread atgraham at gmail dot com
same symbol Product: gcc Version: 4.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: atgraham at gmail dot com GCC host trip

[Bug regression/29248] Stack pointer is modified in functions that don't use the stack

2006-09-26 Thread atgraham at gmail dot com
--- Comment #3 from atgraham at gmail dot com 2006-09-27 04:28 --- Ack! Sorry--I had indicated the wrong target on that one. The target is vxworks, not linux. My 4.1.1 powerpc-linux compiler *does* get this optimization right. So something in the vxworks-specific code is causing

[Bug regression/29248] New: Stack pointer is modified in functions that don't use the stack

2006-09-26 Thread atgraham at gmail dot com
nedTo: unassigned at gcc dot gnu dot org ReportedBy: atgraham at gmail dot com GCC host triplet: i686 GCC target triplet: powerpc-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29248

[Bug c/28808] Alignment problem in __gthread_once_t in vxWorks

2006-08-22 Thread atgraham at gmail dot com
--- Comment #1 from atgraham at gmail dot com 2006-08-22 18:43 --- Patch was submitted to gcc-patches earlier, which is the same as the patch already posted to the previous comment. http://gcc.gnu.org/ml/gcc-patches/2006-08/msg00786.html -- atgraham at gmail dot com changed

[Bug c/28808] New: Alignment problem in __gthread_once_t in vxWorks

2006-08-22 Thread atgraham at gmail dot com
dot org ReportedBy: atgraham at gmail dot com GCC target triplet: powerpc-vxworks-elf http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28808

[Bug middle-end/28493] [4.1/4.2 Regression] Wrong address of stack object used for destructor call on PPC

2006-08-14 Thread atgraham at gmail dot com
--- Comment #14 from atgraham at gmail dot com 2006-08-14 18:16 --- The following patch to the 4.1.1 release code appears to fix the problem. Though I have not been able to convince myself that this is the CORRECT solution to the problem (and am doubtful that it is), testing this fix

[Bug middle-end/28493] [4.1/4.2 Regression] Wrong address of stack object used for destructor call on PPC

2006-08-10 Thread atgraham at gmail dot com
--- Comment #13 from atgraham at gmail dot com 2006-08-11 02:42 --- The problem goes away (at least in this case) at optimization levels -O[s123] (but remains at -O0) when compiling with -fstack-protector. Of course, that's not really an acceptable workaround for most people aff

[Bug middle-end/28493] [4.1/4.2 Regression] Wrong address of stack object used for destructor call on PPC

2006-08-08 Thread atgraham at gmail dot com
--- Comment #12 from atgraham at gmail dot com 2006-08-09 01:30 --- (In reply to comment #11) [...] > it may be a problem with WRS running initializers or > initializing the frame tables. Both of the gcc builds I'm testing with are cross compilers (host i686-pc-linux-gnu):

[Bug target/28493] Wrong address of stack object used for destructor call on PPC

2006-08-08 Thread atgraham at gmail dot com
--- Comment #8 from atgraham at gmail dot com 2006-08-08 23:21 --- (In reply to comment #7) > I don't get any failures with the 4.0-branch for powerpc-linux with sjlj > exceptions. Here's the executable test case I'm using for a regression hunt: Janis, Thank you

[Bug target/28493] Wrong address of stack object used for destructor call on PPC

2006-08-05 Thread atgraham at gmail dot com
--- Comment #4 from atgraham at gmail dot com 2006-08-05 21:11 --- Actually, it turns out that gcc versions before the 4.1 series all get it wrong too, at -O0. The bug gets masked when introducing optimization. Here is the -O0 output from 4.0.3: g++-4.0.3 -O0 -msoft-float -mcpu=405

[Bug target/28493] Wrong address of stack object used for destructor call on PPC

2006-08-05 Thread atgraham at gmail dot com
--- Comment #3 from atgraham at gmail dot com 2006-08-05 16:58 --- This may not be related to 19774 as I had originally thought. This failure case is new as of 4.1.0. GCC version 4.0.3 gets it right: g++-4.0.3 -Os -msoft-float -mcpu=405 -c bug.cc -fno-inline -Wall -dA

[Bug middle-end/26983] [4.0/4.1/4.2 Regression] Missing label with builtin_setjmp/longjmp

2006-08-02 Thread atgraham at gmail dot com
--- Comment #7 from atgraham at gmail dot com 2006-08-02 17:03 --- Is it possible that #28493 is a symptom of the same problem? Does anyone build the darwin compiler with SjLj exceptions? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26983

[Bug target/28493] Wrong address of stack object used for destructor call on PPC

2006-07-26 Thread atgraham at gmail dot com
--- Comment #2 from atgraham at gmail dot com 2006-07-27 02:47 --- This bug appears to only happen when the compiler is built with SjLj exceptions. When the compiler is built for dwarf2 exceptions, this test case (and my original problem area) are both correct: : 0: 94

[Bug target/28493] Wrong address of stack object used for destructor call on PPC

2006-07-26 Thread atgraham at gmail dot com
--- Comment #1 from atgraham at gmail dot com 2006-07-26 15:42 --- Actually, the for loop is unnecessary. Here's a shorter version that displays the same problem: struct Command { virtual ~Command() {} }; void tryfunc() { Command cmd; throw 1; } -- http://gcc.gn

[Bug c++/28493] New: Wrong address of stack object used for destructor call on PPC

2006-07-26 Thread atgraham at gmail dot com
ned at gcc dot gnu dot org ReportedBy: atgraham at gmail dot com GCC host triplet: i686-pc-linux-gnu GCC target triplet: powerpc-wrs-vxworks http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28493

[Bug rtl-optimization/26069] Runtime endian-ness check is no longer optimized out.

2006-02-01 Thread atgraham at gmail dot com
--- Comment #1 from atgraham at gmail dot com 2006-02-02 05:02 --- I've also confirmed the following: The optimization also works on gcc 2.95.2 It does not work on gcc 4.0.2 -- atgraham at gmail dot com changed: What|Removed |

[Bug rtl-optimization/26069] New: Runtime endian-ness check is no longer optimized out.

2006-02-01 Thread atgraham at gmail dot com
ime endian-ness check is no longer optimized out. Product: gcc Version: 4.0.2 Status: UNCONFIRMED Severity: major Priority: P3 Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: atgraham at