public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/30364] [4.1/4.2/4.3 Regression] Wrong variable ranges due to constant folding Date: Fri, 05 Jan 2007 21:06:00 -0000 [thread overview] Message-ID: <20070105210643.13237.qmail@sourceware.org> (raw) In-Reply-To: <bug-30364-7904@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from gdr at integrable-solutions dot net 2007-01-05 21:06 ------- Subject: Re: [4.1/4.2/4.3 Regression] Wrong variable ranges due to constant folding "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes: | Do the parenthesis matter in C? Yes, see paragraphes 11 dowward in the section 5.1.2.3. | They do matter in say Fortran, but in C I | think | (a - 20) + (b - 20) can be evaluated as (a + b) + (-20 + -20) or a - 20 - 20 + | b while that is permitted by the fortran standard, it is my understanding that *existing* practice has fortran compilers refrain from messing with parenthesis. However, this has become a middle-end issue; so I guess I must voice the concern for languages where unconditional re-association is not permitted. The C and C++ languages are example of those. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30364
next prev parent reply other threads:[~2007-01-05 21:06 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-04 9:16 [Bug c/30364] New: " guillaume dot melquiond at ens-lyon dot fr 2007-01-04 9:30 ` [Bug middle-end/30364] [4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org 2007-01-04 10:15 ` guillaume dot melquiond at ens-lyon dot fr 2007-01-04 10:23 ` pinskia at gcc dot gnu dot org 2007-01-04 10:26 ` pinskia at gcc dot gnu dot org 2007-01-04 10:40 ` pinskia at gcc dot gnu dot org 2007-01-04 11:25 ` guillaume dot melquiond at ens-lyon dot fr 2007-01-05 19:06 ` jakub at gcc dot gnu dot org 2007-01-05 19:58 ` pinskia at gcc dot gnu dot org 2007-01-05 20:32 ` pinskia at gcc dot gnu dot org 2007-01-05 21:06 ` gdr at integrable-solutions dot net [this message] 2007-01-05 21:09 ` gdr at integrable-solutions dot net 2007-02-05 5:50 ` mmitchel at gcc dot gnu dot org 2007-02-14 9:03 ` mmitchel at gcc dot gnu dot org 2007-02-21 14:24 ` rguenth at gcc dot gnu dot org 2007-02-28 21:57 ` rguenth at gcc dot gnu dot org 2007-02-28 23:03 ` [Bug middle-end/30364] [4.1/4.2 " rguenth at gcc dot gnu dot org 2007-03-05 13:15 ` rguenth at gcc dot gnu dot org 2007-03-05 13:17 ` [Bug middle-end/30364] [4.1 " rguenth at gcc dot gnu dot org 2007-03-15 18:09 ` rguenth at gcc dot gnu dot org 2007-03-15 18:10 ` rguenth at gcc dot gnu dot org 2007-08-24 16:33 ` jakub at gcc dot gnu dot org 2007-08-24 16:40 ` 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=20070105210643.13237.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).