public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldot at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/30762] inlining destroys type information Date: Sun, 11 Feb 2007 10:24:00 -0000 [thread overview] Message-ID: <20070211102415.4592.qmail@sourceware.org> (raw) In-Reply-To: <bug-30762-11811@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from aldot at gcc dot gnu dot org 2007-02-11 10:24 ------- Created an attachment (id=13031) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13031&action=view) reduced from gcc/double-int.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30762
next prev parent reply other threads:[~2007-02-11 10:24 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-11 10:23 [Bug c/30762] New: " aldot at gcc dot gnu dot org 2007-02-11 10:24 ` [Bug c/30762] " aldot at gcc dot gnu dot org 2007-02-11 10:24 ` aldot at gcc dot gnu dot org [this message] 2007-02-11 10:26 ` aldot at gcc dot gnu dot org 2007-02-11 10:28 ` [Bug c/30762] [4.2 Regression] " aldot at gcc dot gnu dot org 2007-02-11 11:05 ` aldot at gcc dot gnu dot org 2007-02-11 11:57 ` aldot at gcc dot gnu dot org 2007-02-11 11:58 ` aldot at gcc dot gnu dot org 2007-02-11 11:59 ` [Bug c/30762] [4.2/4.3 " aldot at gcc dot gnu dot org 2007-02-16 1:57 ` [Bug c/30762] [4.2/4.3 Regression] IMA messes up with inlining pinskia at gcc dot gnu dot org 2007-02-19 21:08 ` mmitchel at gcc dot gnu dot org 2007-03-07 1:38 ` geoffk at gcc dot gnu dot org 2007-03-07 1:52 ` geoffk at gcc dot gnu dot org 2007-03-07 2:02 ` geoffk at gcc dot gnu dot org 2007-03-14 11:02 ` jakub at gcc dot gnu dot org 2007-03-19 23:26 ` jakub at gcc dot gnu dot org 2007-03-19 23:28 ` jakub at gcc dot gnu dot org 2007-03-20 8:09 ` jakub at gcc dot gnu dot org 2007-04-28 4:18 ` kargl 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=20070211102415.4592.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).