https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81996
--- Comment #12 from wschmidt at linux dot vnet.ibm.com ---
Thanks for sorting this out, Alan!
Bill
> On Sep 21, 2017, at 8:30 AM, amodra at gmail dot com
> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81996
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80982
--- Comment #3 from wschmidt at linux dot vnet.ibm.com ---
Hi Carl,
Just FYI, now that you've fixed the bug, and there are no plans to backport the
patch, you should go ahead and set the status of the bug to RESOLVED FIXED. I
know this di
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50181
--- Comment #3 from wschmidt at linux dot vnet.ibm.com ---
Thanks, Steven! I have been on an extended vacation but will have a
look at this shortly. Very likely this was fixed long ago and the
bugzilla not cleaned up.
Bill
On Thu, 2013-12-26
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52937
--- Comment #2 from wschmidt at linux dot vnet.ibm.com 2012-04-12 11:39:37 UTC
---
Sure, I'll get that information today.
On Thu, 2012-04-12 at 09:28 +, rguenth at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?