Bug#701082: gcc generates incorrect code with -O2 compiling libffi example

notfound 701082 4.9 found 701082 gcc-4.9/4.9.1-19 thanks -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54f7dd6d.2060...@philipashmore.com

Bug#701082: gcc generates incorrect code with -O2 compiling libffi example

found 701082 4.9 thanks I recently updated to jessie/sid which comes with gcc-4.9.1 (Debian 4.9.1-19). It's failing in the same place with optimization set to -O0, -O2 and -O3. It works with -O1! -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". T

Bug#701082: gcc-4.7: gcc generates incorrect code with -O2 compiling libffi example

This problem doesn't happen on Ubuntu or on a fresh squeeze install. Then I realised I had gcc 4.4, 4.5 and 4.6 installed as well as 4.7 and 4.8. With 4.4, 4.5 and 4.6, gcc -O2 -o ffi-test ffi-test.c works. With 4.7 and 4.8 it segfaults instead of outputting "This is cool!". -- To UNSUBSCRIBE, e

Bug#701082: gcc-4.7: gcc generates incorrect code with -O2 compiling libffi example

The libffi example works with -O0, -O1 and -O2 on armhf (Raspberry PI). gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.6/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../src/configure -v --with-pkgversion='Debian 4.6.3-14+rpi1' --wi

Bug#701082: gcc-4.7: gcc generates incorrect code with -O2 compiling libffi example

On 23/02/13 09:40, Matthias Klose wrote: Am 23.02.2013 10:24, schrieb Philip Ashmore: I did an apt-get -t experimental install gcc-4.7 gcc-4.8 and updated libffi gcc -O0 -o ffi-test ffi-test.c -lffi ./ffi-test Hello World! This is cool! gcc -O1 -o ffi-test ffi-test.c -lffi ./ffi-test

Bug#701082: gcc-4.7: gcc generates incorrect code with -O2 compiling libffi example

I did an apt-get -t experimental install gcc-4.7 gcc-4.8 and updated libffi gcc -O0 -o ffi-test ffi-test.c -lffi ./ffi-test Hello World! This is cool! gcc -O1 -o ffi-test ffi-test.c -lffi ./ffi-test Hello World! This is cool! gcc -O2 -o ffi-test ffi-test.c -lffi ./ffi-test Hello World! Segme

Bug#701082: gcc-4.7: gcc generates incorrect code with -O2 compiling libffi example

Package: gcc-4.7 Version: 4.7.2-5 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? I'm using libffi5 * What exactly did you do (or not do) that was effective (or ineffective)? I noticed a problem with

Bug#629868: When it changed

This isn't definitive, but a 10 minute binary search of snapshot.debian.org lead me to the point where the size took a dive. If snapshot.debian.org has an ftp interface this would have taken less time. http://snapshot.debian.org/archive/debian/20100501T040743Z/pool/main/g/gcc-4.5/ - libstdc++6

Bug#630441: g++-4.6 miscompilation

"reference to a char *" should read "reference to a char * on the stack" -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e7d6c7a.1070...@philipashmore.com

Bug#630441: g++-4.6 miscompilation

::unpack_data returns a reference to a char *, which gets stepped on when optimized. Regards, Philip Ashmore -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e7d65cb.2020...@philipashmore.com

Bug#630441: g++-4.6 miscompilation

I'll work on trying to put together a simpler test case. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e7bae3a.9070...@philipashmore.com

Bug#630441: g++-4.6 miscompilation

Hi there. I believe I've tracked down the problem. I've published new versions of v3c(1.9.0-03), treedb(1.1.0-01) and meta-treedb(1.3.0-02) in SourceForge, which gets around this problem. It appears that gcc-4.6 (and clang for that matter) make some dodgy decisions about what appear to be ref

Bug#630441: g++-4.6 miscompilation

- does it build using gcc-snapshot, gcc-4.5 or gcc-4.4? I have gcc and g++ locked to version 4:4.4.5-1, where they work. time sh build.sh (from Message 12 above http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630441#12) ... real6m52.589s user5m37.477s sys 0m31.150s

Bug#630441: g++-4.6 miscompilation

On 04/09/11 17:40, Matthias Klose wrote: On 09/04/2011 06:24 PM, Philip Ashmore wrote: - if you have a working and a non-working build, can you try The build fails due to a test failure caused by the compiler generating incorrect code. If we want to fix this bug then working around it won&#

Bug#630441: g++-4.6 miscompilation

On 04/09/11 15:21, Matthias Klose wrote: tag 630441 moreinfo help thanks On 07/21/2011 12:01 PM, Philip Ashmore wrote: Sorry if I wasn't clear. All the tests pass in the debug (-0O) build. I've got gcc/g++ 4.4.6-6 installed and all the tests pass in debug and release mode. This is

Bug#630441: g++-4.6 miscompilation

I just finished running the tests inside a fresh wheezy 32 bit chroot. The results are the same. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e28066d.3010...@philip

Bug#630441: g++-4.6 miscompilation

Sorry if I wasn't clear. All the tests pass in the debug (-0O) build. I've got gcc/g++ 4.4.6-6 installed and all the tests pass in debug and release mode. This is a problem with the g++ 4.6 release (-03) optimization. Philip -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org wi

Bug#630441: g++-4.6 miscompilation

This fails with g++-4.6.1-4 from testing at the same place. I've updated the packages in sourceforge, so no patches are needed. I've attached a revised build.sh which runs the tests with the current versions. I was about to dive into a rant about "why didn't you try this before releasing gcc/g++

Bug#631627: gcc-defaults version 4:4.4.5-1 non-functional on Wheezy (missing libgcc_s.so)

I did an apt-get update to Sid/unstable and the problem seems to have gone away. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e07acb8.5030...@philipashmore.com

Bug#631627: gcc-defaults version 4:4.4.5-1 non-functional on Wheezy (missing libgcc_s.so)

Package: gcc Version: 4:4.6.0-5 Severity: grave Justification: renders package unusable Here's a simple test program

Bug#630585: gcc-4.4: No gcc dependency package for gcc-4.5

Package: gcc-4.4 Version: 4.4.6-3 Severity: normal I typed "reportbug gcc", but reportbug stated: "gcc is a dependency package. Which of the following packages is the bug in?" forcing me to choose gcc-4.4. I cannot pin gcc to gcc version 4:4.5.3-1 (testing) because that version doesn't exist.

Bug#630441: g++-4.6.0-10 miscompilation

++--- 4 files changed, 17 insertions(+), 8 deletions(-) diff --git a/ChangeLog b/ChangeLog index 2dafda9..e1ac676 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2011-06-14 Philip Ashmore + +* Version 1.8.2-03 + +* changes to v3c.cpp for gcc-4.6 + 2011-06-07 Ph

Bug#629868: libstdc++.tag not installed by libstdc++6-4.5-doc

Package: libstdc++6-4.5-doc Version: 4.5.3-1 Severity: normal My v3c project looks for libstdc++.tag when configuring. This file is installed by libstdc++6-4.4-doc, but it appears to have been dropped. If doxygen support is being dropped, is doxygen being dropped too? It's also not present in l

Bug#590008: cpp-4.4: incorrect macro expansion when a macro call results in the same macro being called

I guess what I'm trying to say is that a global replacement macro (like abc) shouldn't depend on how the tokens came into existence, whether they were typed in or the result of preprocessing. Here's a variant of my original sample that works as expected: #define append_c(X) X##c #define pr

Bug#590038: Update

I downloaded and built gcc/g++-4.5, and got the same problem. I was about to report a bug directly to gcc.gnu.org where I read http://gcc.gnu.org/bugs/#known -> C -> Casting does not work as expected when optimization is turned on. adding -fstrict-aliasing to the compiler command line solved the

Bug#590038: g++-4.4: g++ generates incorrect code with optimisation

I forgot to mention that treedb-0.6.0-beta1 is only accessible from GIT. To get it run $ git clone git://treedb.git.sourceforge.net/gitroot/treedb/treedb -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o

Bug#590038: g++-4.4: g++ generates incorrect code with optimisation

Package: g++-4.4 Version: 4.4.4-6 Severity: important I've uploaded treedb-0.6.0-beta1 to SourceForge as it demonstrates the problem. It uses v3c-1.6.0 which you can download from http://sourceforge.net/projects/v3c/ . The Changelog details the problem, but in summary: $ make check has no probl

Bug#590008: cpp-4.4: incorrect macro expansion when a macro call results in the same macro being called

Package: cpp-4.4 Version: 4.4.4-6 Severity: normal Here's an example #define appendc(x) x##c #define aXc(X) appendc(a##X) #define abc appendc(abb) int aXc(b) = 0; // appendc(ab) -> abc -> appendc(abb) -> abbc int main(int argc, char *argv[]) { return abbc; }

Bug#588120: close

close I missed the last line in kate. My bad. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c315e4b.3000...@philipashmore.com

Bug#588120: g++-4.4: g++ can't handle -E

Package: g++-4.4 Version: 4.4.4-5 Severity: normal I use a lot of preprocessing macros in my projects. When they get out of hand I re-run gcc with -E to see what the compiler sees. I just tried the same with g++: ( cd build/v3c/1-pinwheel && g++ -E -DHAVE_CONFIG_H -I. -I../../../v3c/1-pinwheel -I

Bug#540640: libstdc++6-4.3-dbg is not useful

Two points: 1. The libstdc++6-4.3-dbg library was installed - see the "Listing installed packages matching libstdc++6*". Have you tried running the script? 2. I thought that the idea of a "-dbg" library was to supply the source code at a fixed, known location and the stripped debugging informat

Bug#569902: gcc-4.3: gcc/g++ generates incorrect code with -O2

I enabled the Squeeze repository and installed gcc/g++. gcc version 4.4.3 20100108 (prerelease) (Debian 4.4.2-9) All 8 tests pass in debug and release mode. Philip -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@l

Bug#569902: gcc-4.3: gcc/g++ generates incorrect code with -O2

Package: gcc-4.3 Version: 4.3.2-1.1 Severity: important Steps to reproduce: === Download v3c-1.3.8 from http://sourceforge.net/projects/v3c/ and unpack/build/install it. Download treedb-0.0.1 from http://sourceforge.net/projects/treedb/ and unpack it. cd treedb make release c

Bug#540640: libstdc++6-4.3-dbg is not useful

I wrote a bash script to reproduce this bug - please find it attached. I snipped the i_chunk_stream classes from my SourceForge project http://sourceforge.net/projects/v3c. For some reason gdb insists on a final from the keyboard before it quits even though it's run from a script. To get a

Bug#541300: gcc: 'CXXFLAGS="-g -ggdb -O0" debuild -us -uc' runs out of memory

Package: gcc Version: 4:4.3.2-2 Severity: normal I will attach the output I captured using this command CXXFLAGS="-g -ggdb -O0" nice -n 10 debuild -us -uc 2>&1 | tee make.txt I'm no gcc build expert, so someone should take a look at this. WARNING: program timed out. FAIL: gcc.c-tortu

Bug#540640: libstdc++6-4.3-dbg is not useful

Package: libstdc++6-4.3-dbg Version: 4.3.2-1.1 Severity: important I'm writing classes that derive from istream and streambuf so I need to see how they're called. To do this I installed libstdc++6-4.3-dbg and fired up kdbg. libstdc++6-4.3-dbg seems to make no difference - I still can't step into

Bug#538647: closed by Florian Weimer (Re: Bug#538647: g++-4.3: g++ examines second value to "?" always if it is a template)

* Philip Ashmore: /*HERE*/enum { value = (wanted <= guess) ? result : next_value_type::value }; Not a bug. You need to implement your own conditional operator at the template level to make this work. The version with ?: is not valid C++ Not valid C++ ? My C++ compiler

Bug#538647: g++-4.3: g++ examines second value to "?" always if it is a template

Package: g++-4.3 Version: 4.3.2-1.1 Severity: important Let an example do the talking template< unsigned int result, unsigned int wanted, unsigned int guess > struct log2_calculator; // Specialisation that ends recursion. template< unsigned int result, unsigned int wanted >