public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/43212] [LTO] error: control flow in the middle of basic block Date: Thu, 08 Apr 2010 10:43:00 -0000 [thread overview] Message-ID: <20100408104309.7590.qmail@sourceware.org> (raw) In-Reply-To: <bug-43212-16926@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from steven at gcc dot gnu dot org 2010-04-08 10:43 ------- Should LTO reject function declarations with incompatible attributes? Or should the "discovery" of the attribute in one translation unit be used to update the control flow graph in the other units (e.g. by writing out summaries for the attributes and have a stage in LTO that merges them)? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43212
next prev parent reply other threads:[~2010-04-08 10:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-28 15:21 [Bug lto/43212] New: " d dot g dot gorbachev at gmail dot com 2010-03-01 10:44 ` [Bug lto/43212] " rguenth at gcc dot gnu dot org 2010-04-08 10:43 ` steven at gcc dot gnu dot org [this message] 2010-04-08 11:24 ` rguenth at gcc dot gnu dot org 2010-04-23 16:25 ` rguenth at gcc dot gnu dot org 2010-07-24 16:47 ` rguenth at gcc dot gnu dot org 2010-07-24 16:50 ` rguenth 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=20100408104309.7590.qmail@sourceware.org \ --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).