public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/22017] [3.4/4.0/4.1/4.2 Regression] Error to pass struct parameter when compile with -mrtd Date: Thu, 16 Feb 2006 12:29:00 -0000 [thread overview] Message-ID: <20060216122923.28797.qmail@sourceware.org> (raw) In-Reply-To: <bug-22017-10808@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from pinskia at gcc dot gnu dot org 2006-02-16 12:29 ------- Milestone should be 4.0.3 pre agreement with GDR and Mark. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2005-06-12 15:08:24 |2006-02-16 12:29:22 date| | Target Milestone|3.4.6 |4.0.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22017
next prev parent reply other threads:[~2006-02-16 12:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-22017-10808@http.gcc.gnu.org/bugzilla/> 2005-10-22 21:52 ` [Bug target/22017] [3.4/4.0/4.1 Regression] Error to pass struct parameter when compile with mingw's gcc.exe using "-march=i386 -mrtd" flags pinskia at gcc dot gnu dot org 2005-10-31 3:45 ` mmitchel at gcc dot gnu dot org 2005-10-31 4:30 ` dannysmith at users dot sourceforge dot net 2006-02-16 11:31 ` [Bug target/22017] [3.4/4.0/4.1/4.2 Regression] Error to pass struct parameter when compile with -mrtd rguenth at gcc dot gnu dot org 2006-02-16 12:29 ` pinskia at gcc dot gnu dot org [this message] 2006-02-16 13:22 ` rguenth at gcc dot gnu dot org 2006-02-16 13:25 ` rguenth at gcc dot gnu dot org 2006-02-16 13:34 ` rguenth at gcc dot gnu dot org 2006-02-16 13:36 ` rguenth at gcc dot gnu dot org 2006-02-16 15: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=20060216122923.28797.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).