public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: franord@msn.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: other/10184: unsigned long long arithmetics incorrect Date: Fri, 21 Mar 2003 15:21:00 -0000 [thread overview] Message-ID: <20030321152129.28706.qmail@sources.redhat.com> (raw) Synopsis: unsigned long long arithmetics incorrect State-Changed-From-To: open->feedback State-Changed-By: bangerth State-Changed-When: Fri Mar 21 15:21:28 2003 State-Changed-Why: We need a complete, self-contained testcase to reproduce this. Please review http://gcc.gnu.org/bugs.html to see what is required. Also note that gcc2.96 is not an FSF released version. It is also rather old. Can you check whether the same problem still happens with a newer version, such as gcc 3.2.2? Thanks Wolfgang http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10184
next reply other threads:[~2003-03-21 15:21 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-21 15:21 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-21 14:56 franord
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=20030321152129.28706.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=franord@msn.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).