severity 635126 serious
thanks

With my sparc port maintainer hat on, I'm setting severity of this bug
back to serious. --ftree-sre is on by default for -O2, so pretty much
every sparc binary in the archive is potentially affected by it. The
fact that the test code does not do anything exotic to trigger it
(well, nothing that I can see) convinces me that it should be fixed
before we can release.

Best regards,
--
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC



--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111125190143.GA4575@wooyd.org">http://lists.debian.org/20111125190143.GA4575@wooyd.org

On 11/25/2011 08:01 PM, Jurij Smakov wrote:
> severity 635126 serious
> thanks
>
> With my sparc port maintainer hat on, I'm setting severity of this bug
> back to serious.

is the sparc maintainer information now correctly documented?
http://www.debian.org/ports/sparc/ still shows Ben Collins (not active as a
Debian GCC sparc porter either),
http://release.debian.org/wheezy/arch_qualify.html shows two maintainers.

> --ftree-sre is on by default for -O2, so pretty much
> every sparc binary in the archive is potentially affected by it. The
> fact that the test code does not do anything exotic to trigger it
> (well, nothing that I can see) convinces me that it should be fixed
> before we can release.

thanks for the testcase. please could you forward the report, including
preprocessed source?

thanks, Matthias


--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4ED0F0DE.1020207@debian.org">http://lists.debian.org/4ED0F0DE.1020207@debian.org

On Sat, Nov 26, 2011 at 02:59:58PM +0100, Matthias Klose wrote:

> is the sparc maintainer information now correctly documented?
> http://www.debian.org/ports/sparc/ still shows Ben Collins (not active as a
> Debian GCC sparc porter either),

I don't see Ben's name mentioned anywhere on this page, so I guess you
mean http://www.debian.org/ports/sparc/porting, which does appear to
be out of date.

> http://release.debian.org/wheezy/arch_qualify.html shows two maintainers.

I'm pretty sure I'm one of them :-). Another one is probably Aurelien
Jarno, who is mostly involved with the new sparc64 port.

Best regards,
--
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC


--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111126170927.GA3480@wooyd.org">http://lists.debian.org/20111126170927.GA3480@wooyd.org

On 11/26/2011 06:09 PM, Jurij Smakov wrote:
> On Sat, Nov 26, 2011 at 02:59:58PM +0100, Matthias Klose wrote:
>
>> is the sparc maintainer information now correctly documented?
>> http://www.debian.org/ports/sparc/ still shows Ben Collins (not active as a
>> Debian GCC sparc porter either),
>
> I don't see Ben's name mentioned anywhere on this page, so I guess you
> mean http://www.debian.org/ports/sparc/porting, which does appear to
> be out of date.

right.

>> http://release.debian.org/wheezy/arch_qualify.html shows two maintainers.
>
> I'm pretty sure I'm one of them :-). Another one is probably Aurelien
> Jarno, who is mostly involved with the new sparc64 port.

well, I would like to hear that from himself. My impression is that he doesn't
want to get involved with every port

thanks for forwarding the report. Please could you check the test case with 4.4,
4.5 and trunk (gcc-snapshot) as well, and add the information to the upstream
report?

Matthias


--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4ED2B666.40100@debian.org">http://lists.debian.org/4ED2B666.40100@debian.org