Bug#688587: gcc-4.6: g++-4.6-10 ice on valid code

Matthias, I first wanted to get back to something working for me, i.e. 4.6.3-8. I will upload later today (more probably provide some link to) some failing preprocessed files. Best regards C. On Sun, Sep 23, 2012 at 11:49 PM, Matthias Klose wrote: > you didn't provide the preprocessed source.

g++-4.6.3-10 has massive ice

Dear Debian GCC maintainers, with 4.6.3-10 I get massive ice (on almost all C++ object files I compile). To fix that I reverted to -8. I reported this but didn't get the email from the BTS nor does it show in the bugs database yet. 4.7-x is in a similar state for me since it generates also faulty

Bug#688587: gcc-4.6: g++-4.6-10 ice on valid code

Package: gcc-4.6 Version: 4.6.3-10 Severity: serious Tags: upstream Justification: g++-4.6 ice on valid c++ code since -10 (possibly -9) Dear Maintainer, * What led up to the situation? upgrading gcc-4.6 from -8 to -10 * What exactly did you do (or not do) that was effective (or inef

Bug#676729: feel++: FTBFS: operators.hpp:722:1: internal compiler error: Segmentation fault

Hello I will certainly build-depend on gcc-4.6 for now. However I am very dubious as to gcc47 quality: from one debian version to another it breaks packages, it generates buggy codes. It just doesn't seem very reliable and production ready. Best regards C. On Sun, Jun 10, 2012 at 11:07 PM, Touko

Gcc47 -12 breaks Feel++

Dear Gcc maintainers, gcc47 -12 breaks feel++ compilation. it generates ices and sometimes generates new compiling errors that -11 didn't have. I am very distressed to have this kind of unstable compiler behavior and especially at a time where I don't have much time to work on my packages. Best

Re: Processed: severity of 673749 is important

reopen 673749 thanks On Sat, Jun 9, 2012 at 1:13 PM, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > >> severity 673749 important > Bug #673749 {Done: Matthias Klose } [g++-4.7] g++-4.7: gcc47 > generates buggy code  with optimisation flags > Severity set

Fwd: Bug#676729: feel++: FTBFS: operators.hpp:722:1: internal compiler error: Segmentation fault

Hello I get an ice with gcc47 (see email below) I am trying to reproduce it. Shouldn't it be considered a gcc47 bug rather than a feel++ bug ? Feel++ compiles and runs fine with gcc45, gcc46 and clang31. Best regards C. -- Forwarded message -- From: Lucas Nussbaum Date: Sat, Ju

Bug#673749: still segfault with 4.7.0-9

22, 2012 at 8:51 PM, Christophe Prud'homme wrote: > Hi > > I just tried with the latest 4.7.0-9 and it still segfaults :( > > Best regards > C. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact li

Bug#673749: still segfault with 4.7.0-9

Hi I just tried with the latest 4.7.0-9 and it still segfaults :( Best regards C.

Bug#673749: g++-4.7: gcc47 generates buggy code with optimisation flags

FYI I have also submitted a bug report on GCC Bugzilla [1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53439 On Mon, May 21, 2012 at 11:31 AM, Christophe Prud'homme wrote: > Please note that > - Debug -g > - RelWithDebInfo uses -g -O1 > - Release uses -O3 > > there m

Bug#673749: g++-4.7: gcc47 generates buggy code with optimisation flags

Please note that - Debug -g - RelWithDebInfo uses -g -O1 - Release uses -O3 there must be an option in -O1 that generates the buggy code. Best regards C. On Mon, May 21, 2012 at 10:34 AM, Christophe Prud'homme wrote: > Package: g++-4.7 > Version: 4.7.0-8 > Severity:

Bug#673749: g++-4.7: gcc47 generates buggy code with optimisation flags

Package: g++-4.7 Version: 4.7.0-8 Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? I ported feel++ to gcc47 and found out that it generates buggy code(generating segfault) in optimisation mode. Here are the steps to reproduce it - install feel++-apps - execute

Re: /usr/lib/libgfortranbegin.a missing ?

Matthias thanks for your answer but on alpha somehow cmake does not find this file. I don't have this issue with any of the other platforms. I have been build-depending on gfortran Best regards C. On Mon, Feb 15, 2010 at 8:49 PM, Matthias Klose wrote: > On 15.02.2010 20:38, Ch

/usr/lib/libgfortranbegin.a missing ?

Dear Debian Gcc maintainers, I am porting a package called life [1] on s390, armel and alpha. On alpha, the library compiles fine until I get this message *** No rule to make target `/usr/lib/libgfortranbegin.a', Any idea why this happens? anything particular I should know about gfortran on alph

Bug#434274: gcc-snapshot 20070720-1 fails to compile trivial code

Package: gcc-snapshot Severity: serious Martin, Matthias, it seems that the 20070720-1 snapshot has some issues with limits.h here is a snippet that cannot be compiled by gcc-snapshot --- #include int main() { return 0; } -- /usr/lib/gcc-snapshot/bin/g++ -o t t.cpp

Bug#191149: breaks more than update-menus

Hi, Actually it breaks c++ codes in general Here is the C++file output c++filt _ZNSt9basic_iosIcSt11char_traitsIcEE4initEPSt15basic_streambufIcS1_E std::basic_ios >::init(std::basic_streambuf >*) Switching to my testing box now ;) Best regards C. -- | Christophe Prud'