Bug#676558: gcc-4.6: Incorrect assembly code generated for loop over char ** in named sections

2012-06-12 Thread Chris
On 12/06/2012 7:40 AM, Matthias Klose wrote: [...] please could you recheck with 4.7 from unstable? I just installed unstable/sid and tested against gcc 4.7.0-13. The bug is also present in this version. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "uns

Bug#676558: gcc-4.6: Incorrect assembly code generated for loop over char ** in named sections

2012-06-12 Thread Chris
On 12/06/2012 7:40 AM, Matthias Klose wrote: [...] please could you recheck with 4.7 from unstable? I did not get 4.7 from unstable installed, so I checked against 4.7 from testing instead [gcc version 4.7.0 (Debian 4.7.0-8)]. I found that version 4.7.0-8 has this bug too. -- To UNSUBSCR

Bug#676558: gcc-4.6: Incorrect assembly code generated for loop over char ** in named sections

2012-06-12 Thread Matthias Klose
On 07.06.2012 21:11, Christoph Schwarz wrote: > Package: gcc-4.6 > Version: 4.6.3-1 > Severity: normal > > Dear Maintainer, > > I have a program that loops over const char * pointers in named sections. > In this loop, incorrect generated assembly code causes wrong output, e.g. > it outputs (null)

Bug#676558: gcc-4.6: Incorrect assembly code generated for loop over char ** in named sections

2012-06-07 Thread Christoph Schwarz
Package: gcc-4.6 Version: 4.6.3-1 Severity: normal Dear Maintainer, I have a program that loops over const char * pointers in named sections. In this loop, incorrect generated assembly code causes wrong output, e.g. it outputs (null) instead of the string pointed to by the const char * pointer. T