public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "1319 at bot dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/14863] [3.4 regression] unit-at-a-time causes miscompilation
Date: Wed, 07 Apr 2004 11:56:00 -0000	[thread overview]
Message-ID: <20040407115557.1001.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040406114325.14863.rguenth@tat.physik.uni-tuebingen.de>


------- Additional Comments From 1319 at bot dot ru  2004-04-07 11:55 -------
I have just found that this bug can be triggered on/off using --param
large-function-insns=<something> option. Default value of this changed from
10000 before gcc-3_4-branch creation to 3000 shortly after.

All versions of 3.4.0 and 3.5.0 I tried (20040116..now) are OK with '-O1
-funit-at-a-time --param large-function-insns=10000' and all failed with '-O1
-funit-at-a-time --param large-function-insns=3000'.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14863


  parent reply	other threads:[~2004-04-07 11:56 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06 11:43 [Bug optimization/14863] New: " rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-06 11:45 ` [Bug optimization/14863] " rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-06 11:49 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-06 12:36 ` pinskia at gcc dot gnu dot org
2004-04-06 23:48 ` 1319 at bot dot ru
2004-04-07  7:59 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-07  8:00 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-07  8:04 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-07 10:25 ` 1319 at bot dot ru
2004-04-07 11:56 ` 1319 at bot dot ru [this message]
2004-04-07 12:04 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-07 13:07 ` [Bug optimization/14863] [3.4/3.5 " pinskia at gcc dot gnu dot org
2004-04-07 13:26 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-07 13:37 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-07 13:44 ` giovannibajo at libero dot it
2004-04-07 16:08 ` pinskia at gcc dot gnu dot org
2004-04-07 20:55 ` pinskia at gcc dot gnu dot org
2004-04-08 11:57 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-08 11:58 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-09 13:09 ` pinskia at gcc dot gnu dot org
2004-04-09 13:12 ` pinskia at gcc dot gnu dot org
2004-04-09 13:35 ` pinskia at gcc dot gnu dot org
2004-04-10 15:27 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-11  1:06 ` 1319 at bot dot ru
2004-06-02  0:08 ` [Bug rtl-optimization/14863] " belyshev at lubercy dot com
2004-06-02  0:19 ` [Bug rtl-optimization/14863] [3.4 " pinskia at gcc dot gnu dot org
2004-06-02  6:47 ` belyshev at lubercy dot com
2004-06-02  7:38 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-06-02  8:50 ` belyshev at lubercy dot com
2004-06-02 10:18 ` giovannibajo at libero dot it
2004-06-02 10:51 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-06-02 10:57 ` giovannibajo at libero dot it
2004-06-02 11:07 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-06-02 11:14 ` giovannibajo at libero dot it
2004-06-02 11:15 ` belyshev at lubercy dot com
2004-06-02 11:54 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-06-02 12:05 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-06-02 22:30 ` pinskia at gcc dot gnu dot org
2004-06-03  1:01 ` [Bug rtl-optimization/14863] [3.4/3.5 " giovannibajo at libero dot it
2004-06-03  1:08 ` pinskia at gcc dot gnu dot org
2004-06-03  1:12 ` pinskia at gcc dot gnu dot org
2004-06-03  1:25 ` giovannibajo at libero dot it
2004-06-04 20:47 ` giovannibajo at libero dot it

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=20040407115557.1001.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: 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).