public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tbm at cyrius dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/31103] [4.3 Regression] same canonical type node for different types with long int Date: Fri, 09 Mar 2007 12:46:00 -0000 [thread overview] Message-ID: <20070309124612.23670.qmail@sourceware.org> (raw) In-Reply-To: <bug-31103-12387@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from tbm at cyrius dot com 2007-03-09 12:46 ------- Created an attachment (id=13176) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13176&action=view) preprocessed source -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31103
next prev parent reply other threads:[~2007-03-09 12:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-09 12:45 [Bug c++/31103] New: " tbm at cyrius dot com 2007-03-09 12:46 ` tbm at cyrius dot com [this message] 2007-03-09 13:07 ` [Bug c++/31103] " tbm at cyrius dot com 2007-03-09 15:17 ` [Bug c++/31103] [4.3 Regression] same canonical type node for VLAs pinskia at gcc dot gnu dot org 2007-04-03 23:22 ` pinskia at gcc dot gnu dot org 2007-04-05 3:40 ` dgregor at gcc dot gnu dot org 2007-04-12 11:48 ` dgregor at gcc dot gnu dot org 2007-04-12 11:51 ` dgregor at gcc dot gnu dot org 2007-04-12 11:53 ` dgregor 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=20070309124612.23670.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).