public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9123: [3.2/3.3/3.4 regression ] Internal compiler error in do_SUBST at combine.c:434 Date: Fri, 28 Mar 2003 20:36:00 -0000 [thread overview] Message-ID: <20030328200600.9492.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9123; it has been noted by GNATS. From: Eric Botcazou <ebotcazou@libertysurf.fr> To: Jason Merrill <jason@redhat.com> Cc: gcc-bugs@gcc.gnu.org, khindenburg@cherrynebula.net, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: optimization/9123: [3.2/3.3/3.4 regression ] Internal compiler error in do_SUBST at combine.c:434 Date: Fri, 28 Mar 2003 20:54:18 +0100 > Hmm, I seem to have attached the wrong C testcase. To fail, it needs > consts. It fails with 3.2 and 3.3, but seems to be fixed on the trunk. > > typedef unsigned char T; > inline T clamp (const T in, const T min, const T max) > { > return in <= min ? min : in >= max ? max : in; > } > unsigned char f (int i) > { > return clamp (i, 0, 255); > } I can't reproduce on any branch on i586-redhat-linux-gnu. I strongly suspect that I fixed it everywhere two weeks ago with: 2003-03-14 Eric Botcazou <ebotcazou@libertysurf.fr> PR optimization/8396 * tree-inline.c (initialize_inlined_parameters): Make sure the value of read-only constant arguments is passed with the right type. Are your 3.2 and 3.3 compilers up-to-date? -- Eric Botcazou
next reply other threads:[~2003-03-28 20:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-28 20:36 Eric Botcazou [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-28 22:06 ebotcazou 2003-03-28 17:16 Jason Merrill 2003-03-28 10:39 Eric Botcazou 2003-03-22 21:46 Janis Johnson 2003-03-10 22:38 jason 2003-03-10 22:37 jason
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=20030328200600.9492.qmail@sources.redhat.com \ --to=ebotcazou@libertysurf.fr \ --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).