public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug pch/31634] *_SECTION_ASM_OP storage has undocumented constraints Date: Sun, 09 Nov 2014 14:34:00 -0000 [thread overview] Message-ID: <bug-31634-4-G06d0fcOtx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-31634-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31634 --- Comment #4 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> --- 31634 used to be relevant for ARC, but that port has since ceased to support changing the name if TEXT_SECTION_ASM_OP etc. by command line option, and uses now a string literal, precisely in order to work around this bug. Hence, this no longer blocks other/39363 .
next parent reply other threads:[~2014-11-09 14:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-31634-4@http.gcc.gnu.org/bugzilla/> 2014-11-09 14:34 ` amylaar at gcc dot gnu.org [this message] 2007-04-19 17:57 [Bug pch/31634] New: " amylaar at gcc dot gnu dot org 2007-04-19 18:27 ` [Bug pch/31634] " amylaar at gcc dot gnu dot org 2007-05-02 12:43 ` amylaar at gcc dot gnu dot org 2009-03-04 21:56 ` amylaar at gcc dot gnu dot org 2009-03-05 0:27 ` amylaar at gcc dot gnu dot 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-31634-4-G06d0fcOtx@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: linkBe 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).