public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/36998] [4.3/4.4 regression] Ada bootstrap broken on i586-*-*
Date: Sat, 02 Aug 2008 15:03:00 -0000	[thread overview]
Message-ID: <20080802150235.9161.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36998-226@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from kkojima at gcc dot gnu dot org  2008-08-02 15:02 -------
I've tested the 2nd patch on sh4, but it doesn't fix the ICE
on sh4.  Perhaps the problem is slightly different from that
for i586.  Here is a reduced test case for the sh-elf compiler
with the option '-m4 -O -fasynchronous-unwind-tables':

union double_union
{
  double d;
  unsigned int i[2];
};

char *foo (double _d, char *s, char **rve)
{
  union double_union d;

  d.d = _d;
  if ((d.i[1]) & 0x80000000UL)
    (d.i[1]) &= ~0x80000000UL;
  if (((d.i[1]) & 0x7ff00000UL) == 0x7ff00000UL)
    return s;
  if (!d.d)
    {
      s = "0";
      if (rve) *rve = s + 1;
      return s;
    }
}

I've tried to see what is going on in the above test case
with stepping from the top of compute_barrier_args_size_1.
It seems that that function scans insns and updates
cur_args_size as follows:

(insn/f 95 ... (set (reg/f:SI 14 r14) (reg/f:SI 15 r15))...)
...
(insn 91 ... (set (mem/c:SF (pre_dec:SI (reg/f:SI 15 r15))) (reg:SF 68
fr4))...)
cur_args_size is updated to 4.

(insn 92 ... (set (mem/c:SF (pre_dec:SI (reg/f:SI 15 r15))) (reg:SF 69
fr5))...)
cur_args_size is updated to 8.
...
(jump_insn 22 ... (label_ref 77) ...)
...
(insn 86 ... (set (mem/c:DF (pre_dec:SI (reg/f:SI 15 r15))) (reg:DF 6 r6)))
cur_args_size is updated to 16.
...
(jump_insn 33 ... (label_ref 77) ...)
...
;; Exit block
(code_label 77 ...)
...
(insn 102 ... (set (reg/f:SI 15 r15) (reg/f:SI 14 r14)) ...)

Thus label 77 is reachable from (jump_insn 22 ...) where arg_size
is 8 and from (jump_insn 33 ...) where arg_size is 16.


-- 


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


  parent reply	other threads:[~2008-08-02 15:03 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 13:31 [Bug rtl-optimization/36998] New: " ebotcazou at gcc dot gnu dot org
2008-08-01 15:11 ` [Bug rtl-optimization/36998] " jakub at gcc dot gnu dot org
2008-08-01 16:14 ` jakub at gcc dot gnu dot org
2008-08-01 20:03 ` jason at gcc dot gnu dot org
2008-08-02  5:50 ` kkojima at gcc dot gnu dot org
2008-08-02 11:54 ` jakub at gcc dot gnu dot org
2008-08-02 11:59 ` jakub at gcc dot gnu dot org
2008-08-02 15:03 ` kkojima at gcc dot gnu dot org [this message]
2008-08-02 15:18 ` jakub at gcc dot gnu dot org
2008-08-02 15:50 ` ebotcazou at gcc dot gnu dot org
2008-08-02 22:14 ` kkojima at gcc dot gnu dot org
2008-08-08 20:17 ` rguenth at gcc dot gnu dot org
2008-08-09 22:21 ` gerald at pfeifer dot com
2008-08-11  9:37 ` rguenth at gcc dot gnu dot org
2008-08-11  9:45 ` rguenth at gcc dot gnu dot org
2008-08-11 10:25   ` Andrew Thomas Pinski
2008-08-11 10:25 ` jakub at gcc dot gnu dot org
2008-08-11 10:27 ` pinskia at gmail dot com
2008-08-11 10:28 ` jakub at gcc dot gnu dot org
2008-08-11 15:03 ` eric dot weddington at atmel dot com
2008-08-11 15:16 ` jakub at gcc dot gnu dot org
2008-08-11 16:02 ` eric dot weddington at atmel dot com
2008-08-11 16:24 ` jakub at gcc dot gnu dot org
2008-08-11 16:27 ` jakub at gcc dot gnu dot org
2008-08-12  0:28 ` kkojima at gcc dot gnu dot org
2008-08-12  0:31 ` kkojima at gcc dot gnu dot org
2008-08-12 14:50 ` jakub at gcc dot gnu dot org
2008-08-13  3:31 ` kkojima at gcc dot gnu dot org
2008-08-18 15:35 ` rguenth at gcc dot gnu dot org
2008-08-18 20:46 ` ebotcazou at gcc dot gnu dot org
2008-08-27 22:12 ` jsm28 at gcc dot gnu dot org
2008-11-18 20:40 ` ebotcazou at gcc dot gnu dot org
2008-11-20 21:29 ` jakub at gcc dot gnu dot org
2008-11-20 21:53 ` jakub at gcc dot gnu dot org
2008-11-29 22:14 ` ebotcazou 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=20080802150235.9161.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).