public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "davek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/46671] [4.6 Regression] ICE in default_no_named_section, at varasm .c:5994 Date: Mon, 06 Dec 2010 17:27:00 -0000 [thread overview] Message-ID: <bug-46671-4-aQ25wJFdGl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46671-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46671 --- Comment #9 from Dave Korn <davek at gcc dot gnu.org> 2010-12-06 17:27:06 UTC --- (In reply to comment #8) > sdbout.c is broken then. Quite likely, but I don't understand what it thinks it's trying to do yet well enough to be sure how. > If it doesn't care in which code section it emits the > stuff, it should at least not switch_to_section (text_section) if > in_section != NULL && (in_section->flags & SECTION_CODE) != 0. I'll take a look at that possibility, thanks. I'm going to have to read up on the coff debug spec to see what it says about the matter. > And in any case, it should remember in_section from the beginning of the > function into say saved_section automatic var and if it was non-NULL, do > switch_to_section (saved_section) at the end of the function. In fact I don't think that would help, GAS does not accept switching section in the middle of an open CFI directive block (though this is probably an implementation limitation rather than a deliberate design choice; cfi is tracked on a per-frag basis, switching to a new section and back leads to starting a new frag which doesn't have any pointer to the previously-begun cfi block.)
next prev parent reply other threads:[~2010-12-06 17:27 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-26 7:32 [Bug middle-end/46671] New: " danglin at gcc dot gnu.org 2010-11-26 10:33 ` [Bug middle-end/46671] " rguenth at gcc dot gnu.org 2010-11-27 5:36 ` danglin at gcc dot gnu.org 2010-11-27 5:51 ` danglin at gcc dot gnu.org 2010-11-29 13:36 ` ro at gcc dot gnu.org 2010-12-02 3:20 ` danglin at gcc dot gnu.org 2010-12-03 15:22 ` ro at CeBiTec dot Uni-Bielefeld.DE 2010-12-03 17:22 ` dave at hiauly1 dot hia.nrc.ca 2010-12-04 5:37 ` davek at gcc dot gnu.org 2010-12-06 12:47 ` jakub at gcc dot gnu.org 2010-12-06 17:27 ` davek at gcc dot gnu.org [this message] 2010-12-08 1:27 ` danglin at gcc dot gnu.org 2010-12-08 12:29 ` jakub at gcc dot gnu.org 2010-12-08 13:29 ` ro at gcc dot gnu.org 2010-12-08 16:49 ` jakub at gcc dot gnu.org 2010-12-12 20:38 ` hubicka at gcc dot gnu.org 2010-12-15 10:25 ` ro at gcc dot gnu.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-46671-4-aQ25wJFdGl@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).