public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/3386] [3.3/3.4 Regression] Undocumented target macros in 3.0
Date: Fri, 11 Jul 2003 23:38:00 -0000	[thread overview]
Message-ID: <20030711233841.13552.qmail@sources.redhat.com> (raw)
In-Reply-To: <20010622174601.3386.jsm28@cam.ac.uk>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From pinskia at physics dot uc dot edu  2003-07-11 23:38 -------
There really is no easy way to find out what are the new ones that got not documented, I 
tried to update the list that was there and add people who added some of the patches 
which added the target macros.


  parent reply	other threads:[~2003-07-11 23:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010622174601.3386.jsm28@cam.ac.uk>
2003-05-24 23:21 ` [Bug other/3386] " pinskia@physics.uc.edu
2003-05-27 17:31 ` pinskia@physics.uc.edu
2003-06-02 15:05 ` hans-peter.nilsson@axis.com
2003-06-02 15:14 ` pinskia@physics.uc.edu
2003-06-04 12:58 ` pinskia@physics.uc.edu
2003-06-28 19:01 ` [Bug other/3386] [3.3/3.4 Regression] " pinskia at physics dot uc dot edu
2003-07-11 23:33 ` steven at gcc dot gnu dot org
2003-07-11 23:38 ` pinskia at physics dot uc dot edu [this message]
2003-07-11 23:40 ` mark at codesourcery dot com
2003-07-12  0:08 ` neroden at gcc dot gnu dot org
2003-07-12  0:10 ` jsm at polyomino dot org dot uk
2003-09-05  5:45 ` mmitchel at gcc dot gnu dot org
     [not found] <20010622174601.3386.jsm-gccbugs@polyomino.org.uk>
2003-10-30 11:29 ` jsm at polyomino dot org dot uk
2003-12-05  2:48 ` 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=20030711233841.13552.qmail@sources.redhat.com \
    --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).