public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: joel@gcc.gnu.org
To: ccj@acm.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	hubicka@gcc.gnu.org, joel@OARcorp.com, nobody@gcc.gnu.org,
	pbarada@mail.wm.sps.mot.com
Subject: Re: target/8343: m68k-elf/rtems ICE at instantiate_virtual_regs_1
Date: Fri, 25 Oct 2002 14:05:00 -0000	[thread overview]
Message-ID: <20021025210518.12399.qmail@sources.redhat.com> (raw)

Synopsis: m68k-elf/rtems ICE at instantiate_virtual_regs_1

Responsible-Changed-From-To: unassigned->hubicka
Responsible-Changed-By: joel
Responsible-Changed-When: Fri Oct 25 14:05:18 2002
Responsible-Changed-Why:
    Tracked to patch you committed. :)
    ===================================
    FInal feedback from Peter.
    
    'cvs update -D "2001/05/19 04:24:49" gcc' works
    'cvs update -D "2001/05/19 04:29:50" gcc' fails
    
    The only thing of interest changing is gcc/gcc/recog.c, from version
    1.102 to version 1.103.
    
    The log for gcc/gcc/recog.c looks like:
    
    revision 1.103
    date: 2001/05/19 08:24:50;  author: hubicka;  state: Exp;  lines: +85 -150
            * recog.c (general_operand): Prohibit nonzero subreg bytes on
            subregs containing mem.
    
    
    This was with the following testcase:
    
    extern unsigned foo;
    unsigned long long
    bar (void)
    {
       unsigned long long t = foo;
       return t * foo;
    }
    
    
    ===================================

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8343


             reply	other threads:[~2002-10-25 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 14:05 joel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-25 16:46 Jan Hubicka
2002-10-25 12:36 Peter Barada
2002-10-25 10:26 Graham Stott
2002-10-25  5:59 joel
2002-10-24 14:56 joel

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=20021025210518.12399.qmail@sources.redhat.com \
    --to=joel@gcc.gnu.org \
    --cc=ccj@acm.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=hubicka@gcc.gnu.org \
    --cc=joel@OARcorp.com \
    --cc=nobody@gcc.gnu.org \
    --cc=pbarada@mail.wm.sps.mot.com \
    /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).