public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ralf_corsepius at rtems dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/17824] Hard-coded AS and LD in c4x.h
Date: Mon, 04 Oct 2004 12:51:00 -0000	[thread overview]
Message-ID: <20041004125105.12468.qmail@sourceware.org> (raw)
In-Reply-To: <20041004043914.17824.ralf_corsepius@rtems.org>


------- Additional Comments From ralf_corsepius at rtems dot org  2004-10-04 12:51 -------
1. The PR is against 3.4-branch, because this is what I am using, what I tested
the patch with and what I am reporting the bug against.

2. The patch applies to HEAD without changes.

3. Why is GCC asking to file PRs to bugzilla, if they are requested to post
patch proposals to gcc-patches afterwards. Sorry, but this is just ineffective.

-- 


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


  parent reply	other threads:[~2004-10-04 12:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04  4:39 [Bug target/17824] New: " ralf_corsepius at rtems dot org
2004-10-04  4:40 ` [Bug target/17824] " ralf_corsepius at rtems dot org
2004-10-04  4:40 ` ralf_corsepius at rtems dot org
2004-10-04 12:18 ` giovannibajo at libero dot it
2004-10-04 12:51 ` ralf_corsepius at rtems dot org [this message]
2004-10-04 12:54 ` pinskia at gcc dot gnu dot org
2004-10-04 13:22 ` ralf_corsepius at rtems dot org
2004-10-04 13:28 ` pinskia at gcc dot gnu dot org
2004-12-12 21:38 ` pinskia at gcc dot gnu dot org
2005-04-06  8:11 ` cvs-commit at gcc dot gnu dot org
2005-04-06  8:15 ` ralf dot corsepius at rtems dot org
2005-04-24  8:10 ` cvs-commit at gcc dot gnu dot org
2005-04-25  3:16 ` cvs-commit at gcc dot gnu dot org
2005-04-25  3:18 ` corsepiu at gcc dot gnu dot org
2005-04-25  3:19 ` pinskia 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=20041004125105.12468.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).