public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dhazeghi at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/11772] Incorrect code generated with -mrtd and long long Date: Sat, 23 Aug 2003 01:07:00 -0000 [thread overview] Message-ID: <20030823010737.29672.qmail@sources.redhat.com> (raw) In-Reply-To: <20030802171123.11772.mikulas@artax.karlin.mff.cuni.cz> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11772 dhazeghi at yahoo dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.4 |---
next prev parent reply other threads:[~2003-08-23 1:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-02 17:11 [Bug c/11772] New: " mikulas at artax dot karlin dot mff dot cuni dot cz 2003-08-02 17:16 ` [Bug c/11772] " pinskia at physics dot uc dot edu 2003-08-02 17:17 ` mikulas at artax dot karlin dot mff dot cuni dot cz 2003-08-02 17:21 ` pinskia at physics dot uc dot edu 2003-08-05 14:43 ` pinskia at physics dot uc dot edu 2003-08-23 1:07 ` dhazeghi at yahoo dot com [this message] 2003-11-23 7:14 ` [Bug target/11772] Incorrect code generated with -mrtd and long long (most builtins) pinskia 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=20030823010737.29672.qmail@sources.redhat.com \ --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).