public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: rearnsha@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: Mon, 25 Mar 2002 05:46:00 -0000	[thread overview]
Message-ID: <20020325134604.5214.qmail@sources.redhat.com> (raw)

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

From: Richard Earnshaw <rearnsha@arm.com>
To: "Baker, Rick" <RBaker@panasonicatlanta.com>
Cc: "'rearnsha@gcc.gnu.org'" <rearnsha@gcc.gnu.org>,
        "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>,
        "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/5836: GCC 3.0.3 fails when compiling inline instructions 
 with 16-bit ARM code.
Date: Mon, 25 Mar 2002 13:42:48 +0000

  
 > Sorry for the delay, I had to recreate the setup.  The patch
 > help one of the problems mentioned with Thumb code and
 > -mlong-calls.  I do not have time to verify it fixed all the
 > issues.  
 
 Thanks, I'll close the PR.
 
 > 
 > Tell me, how can I search for these issues on my own next time.
 > I did the usual searches and found no hits on this subject?
 > 
 
 Not easily in this case.  I happened to know that this had been solved 
 recently, plus trying the test on the trunk build of the compiler 
 confirmed that it was no-longer a problem.  After that it was a matter of 
 sleuthing out the patch that fixed it.
 
 > Anyways...thank-you for your time and effort.
 
 No problem.
 
 R.
 
 


             reply	other threads:[~2002-03-25 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25  5:46 Richard Earnshaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-25  5:36 Baker, Rick
2002-03-22  3:40 rearnsha
2002-03-06  7:26 Baker, Rick
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=20020325134604.5214.qmail@sources.redhat.com \
    --to=rearnsha@arm.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=rearnsha@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).