public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Baker, Rick" <RBaker@panasonicatlanta.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c++/5836: GCC 3.0.3 fails when compiling inline instructions  with 16-bit ARM code.
Date: Wed, 06 Mar 2002 07:26:00 -0000	[thread overview]
Message-ID: <20020306152603.28454.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/5836; it has been noted by GNATS.

From: "Baker, Rick" <RBaker@panasonicatlanta.com>
To: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>, 
	"'nobody@gcc.gnu.org'" <nobody@gcc.gnu.org>
Cc:  
Subject: RE: c++/5836: GCC 3.0.3 fails when compiling inline instructions 
	with 16-bit ARM code.
Date: Wed, 6 Mar 2002 10:17:30 -0500 

 Hello,
 
 Is there any chance this problem will be investigated.  I ask because there
 are many other problems encountered in the same area.  I have been asked
 to make a decision on the GNU tools for future Panasonic development and
 this will, of course, make the tools unusable for us.
 
 Thanks,
 Rick Baker
 
 -----Original Message-----
 From: gcc-gnats@gcc.gnu.org [mailto:gcc-gnats@gcc.gnu.org]
 Sent: Monday, March 04, 2002 1:56 PM
 To: Baker, Rick
 Subject: Re: c++/5836: GCC 3.0.3 fails when compiling inline
 instructions with 16-bit ARM code.
 
 
 Thank you very much for your problem report.
 It has the internal identification `c++/5836'.
 The individual assigned to look at your
 report is: unassigned. 
 
 >Category:       c++
 >Responsible:    unassigned
 >Synopsis:       GCC 3.0.3 fails when compiling inline instructions with
 16-bit ARM code.
 >Arrival-Date:   Mon Mar 04 10:56:00 PST 2002
 --Appended by Matsushita Mobile Communications Development Corporation of
 U.S.A.-----This e-mail and any attachments may contain information that is
 confidential, proprietary, privileged or otherwise protected by law. The
 information is solely intended for the named addressee (or a person
 responsible for delivering it to the addressee). If you are not the intended
 recipient of this message, you are not authorized to read, print, retain,
 copy or disseminate this message or any part of it. If you have received
 this e-mail in error, please notify the sender immediately by return e-mail
 and delete it from your computer. 


             reply	other threads:[~2002-03-06 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06  7:26 Baker, Rick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-25  5:46 Richard Earnshaw
2002-03-25  5:36 Baker, Rick
2002-03-22  3:40 rearnsha
2002-03-04 10:56 rbaker

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=20020306152603.28454.qmail@sources.redhat.com \
    --to=rbaker@panasonicatlanta.com \
    --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: 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).