public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: joel.sherrill@OARcorp.com
Cc: jbuck@synopsys.com, mark@codesourcery.com, bkoz@redhat.com,
	nickc@redhat.com, rearnsha@arm.com, jakub@redhat.com,
	rth@redhat.com, gcc@gcc.gnu.org
Subject: Re: GCC 3.2.1 -- Request for Bug Fixers
Date: Thu, 24 Oct 2002 15:55:00 -0000	[thread overview]
Message-ID: <200210241628.g9OGSA624994@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <3DB7E512.AD642C23@OARcorp.com> (message from Joel Sherrill on Thu, 24 Oct 2002 07:18:26 -0500)


>Also the bug Pater Barada is tracking down seems to impact a number
>of m68k/coldfire users (PR8309).  If someone could fix that in time 
>for 3.2.1, it would be appreciated.
>
>http://gcc.gnu.org/ml/gcc/2002-10/msg01441.html

I just checked out the trunk and it exhibits this bug.  I'm
currently pulling out gcc-3_2-branch to see if its there.
If not, then I'll binary search the gcc-3_2-branch for when it showed
up. 

-- 
Peter Barada                                   Peter.Barada@motorola.com
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)

  reply	other threads:[~2002-10-24 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24  0:36 Mark Mitchell
2002-10-24  0:43 ` Joe Buck
2002-10-24 11:39   ` Joel Sherrill
2002-10-24 15:55     ` Peter Barada [this message]
2002-10-25  6:51 ` Benjamin Kosnik
2002-11-01  7:05 ` Richard Earnshaw
2002-11-01 10:40   ` Joe Buck
2002-11-01 10:48     ` David Edelsohn

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=200210241628.g9OGSA624994@hyper.wm.sps.mot.com \
    --to=pbarada@mail.wm.sps.mot.com \
    --cc=bkoz@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jbuck@synopsys.com \
    --cc=joel.sherrill@OARcorp.com \
    --cc=mark@codesourcery.com \
    --cc=nickc@redhat.com \
    --cc=rearnsha@arm.com \
    --cc=rth@redhat.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).