public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tg at mirbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47908] attribute((optimize(2))) causes ICE in m68k_sched_issue_rate
Date: Wed, 27 Jul 2011 23:29:00 -0000	[thread overview]
Message-ID: <bug-47908-4-uDKdajTFrf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47908-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47908

--- Comment #6 from Thorsten Glaser <tg at mirbsd dot org> 2011-07-27 23:29:13 UTC ---
Mikael, can you please publish your “fully tested patches to fix this for
4.4.5, 4.5.2, and 4.6.0” so we can at least include this in the packages?

If the FSF itself (i.e. gnulib) starts using those pragmas which cause
this ICE, I think we’re going to see more and more popping up; I could
convince the maintainer of libvirt to include the m68k workaround in
his package (compile with -DWRAPV -fwrapv) but that doesn’t really scale.

Without the copyright assignment (WTF is going on there, mine took about
three weeks!) it’s still distributable under GPL, just with you as author.

Thanks!


  parent reply	other threads:[~2011-07-27 23:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26 20:59 [Bug target/47908] New: " mikpe at it dot uu.se
2011-02-26 21:33 ` [Bug target/47908] " mikpe at it dot uu.se
2011-03-01 23:45 ` mikpe at it dot uu.se
2011-04-10 18:36 ` alanh at fairlite dot co.uk
2011-04-11  7:36 ` mikpe at it dot uu.se
2011-07-26 20:57 ` schwab@linux-m68k.org
2011-07-27 23:29 ` tg at mirbsd dot org [this message]
2011-07-29 11:44 ` mikpe at it dot uu.se
2011-07-31 15:01 ` schwab at gcc dot gnu.org
2011-07-31 15:09 ` schwab at gcc dot gnu.org
2011-08-01 13:45 ` owner at bugs dot debian.org
2011-08-22 12:04 ` schwab@linux-m68k.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-47908-4-uDKdajTFrf@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).