public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schlie at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/18665] [3.4/4.0 Regression] -ftrapv borks up simple integer arithmetic
Date: Tue, 07 Dec 2004 14:36:00 -0000 [thread overview]
Message-ID: <20041207143612.16985.qmail@sourceware.org> (raw)
In-Reply-To: <20041124222749.18665.skunk@iskunk.org>
------- Additional Comments From schlie at comcast dot net 2004-12-07 14:36 -------
Subject: [3.4/4.0 Regression] -ftrapv borks up simple
integer arithmetic
> ------- Additional Comment #8 From Eric Botcazou 2004-12-06 18:45
> The (useless?) mode promotion from SImode to DImode comes from:
> http://gcc.gnu.org/ml/gcc-patches/2003-02/msg00625.html
>
The c4X inspired logic seems basically wrong; built-in function type sizes
should likely be determined by the mode/size (QI/HI/SI/etc.) specified by
the target, not words-per-"anything" (where 8-bit targets may define a short
as being 1 word-wide, and long as 4-words-wide; 64-bit targets may specify a
short as being 1/4-words-wide, and long as 1-words-wide).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18665
next prev parent reply other threads:[~2004-12-07 14:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 22:29 [Bug target/18665] New: " skunk at iskunk dot org
2004-11-24 22:32 ` [Bug target/18665] " skunk at iskunk dot org
2004-11-24 22:42 ` pinskia at gcc dot gnu dot org
2004-11-28 0:07 ` steven at gcc dot gnu dot org
2004-11-28 0:22 ` steven at gcc dot gnu dot org
2004-11-28 0:26 ` steven at gcc dot gnu dot org
2004-11-28 0:31 ` [Bug target/18665] [4.0 Regression] " steven at gcc dot gnu dot org
2004-11-28 0:33 ` [Bug target/18665] [3.4/4.0 " pinskia at gcc dot gnu dot org
2004-11-28 0:34 ` steven at gcc dot gnu dot org
2004-11-28 13:00 ` steven at gcc dot gnu dot org
2004-12-06 18:45 ` ebotcazou at gcc dot gnu dot org
2004-12-06 18:47 ` ebotcazou at gcc dot gnu dot org
2004-12-06 20:51 ` rth at gcc dot gnu dot org
2004-12-07 6:59 ` ebotcazou at gcc dot gnu dot org
2004-12-07 14:36 ` schlie at comcast dot net [this message]
2004-12-10 7:35 ` ebotcazou at gcc dot gnu dot org
2004-12-10 9:53 ` ebotcazou at gcc dot gnu dot org
2004-12-10 10:11 ` ebotcazou at gcc dot gnu dot org
2004-12-10 18:59 ` [Bug other/18665] " rth at gcc dot gnu dot org
2004-12-10 19:24 ` ebotcazou at gcc dot gnu dot org
2004-12-10 19:40 ` rth at gcc dot gnu dot org
2004-12-10 20:04 ` ebotcazou at gcc dot gnu dot org
2004-12-10 20:17 ` rth at gcc dot gnu dot org
2004-12-11 9:39 ` ebotcazou at gcc dot gnu dot org
2004-12-11 23:12 ` rth at gcc dot gnu dot org
2004-12-12 7:19 ` ebotcazou at gcc dot gnu dot org
2004-12-13 17:11 ` pinskia at gcc dot gnu dot org
2004-12-14 14:17 ` pinskia at gcc dot gnu dot org
2004-12-14 14:36 ` ebotcazou at gcc dot gnu dot org
2004-12-15 12:31 ` cvs-commit at gcc dot gnu dot org
2004-12-15 12:35 ` cvs-commit at gcc dot gnu dot org
2004-12-15 12:39 ` ebotcazou at gcc dot gnu dot org
2004-12-07 1:16 [Bug target/18665] " Paul Schlie
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=20041207143612.16985.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: link
Be 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).