From: "Dana, Eric" <Eric_Dana@bmc.com>
To: "'Michael Matz'" <matzmich@cs.tu-berlin.de>,
"Dana, Eric" <Eric_Dana@bmc.com>
Cc: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Subject: RE: patch/proposal: obsolete configurations in 3.1
Date: Tue, 16 Apr 2002 12:57:00 -0000 [thread overview]
Message-ID: <C41D82BF5BACD311B1B600A0C9EAF0CF0659BEF2@es01-bos> (raw)
Michael,
Patches have been submitted for post GCC 3.0.4. I'm going to submit
a patch for GCC 3.1 RSN.
--Eric--
-----Original Message-----
From: Michael Matz [mailto:matzmich@cs.tu-berlin.de]
Sent: Tuesday, April 16, 2002 12:31 PM
To: Dana, Eric
Cc: 'gcc@gcc.gnu.org'
Subject: RE: patch/proposal: obsolete configurations in 3.1
Hi,
On Tue, 16 Apr 2002, Dana, Eric wrote:
> i?86-sequent-sysv4*
>
> This is still in use. We use it at my company.
And you have a newer FSF compiler than, say 2.7.2 for it? I.e. does the
current version of GCC work for that target? If not, do you want to make
it work?
Ciao,
Michael.
next reply other threads:[~2002-04-16 19:26 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 12:57 Dana, Eric [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-26 8:46 Dana, Eric
2002-04-26 9:18 ` Janis Johnson
2002-04-16 8:46 Dana, Eric
2002-04-16 9:21 ` 'Zack Weinberg'
2002-04-16 9:39 ` Michael Matz
[not found] <20020412194555.GD320@codesourcery.com.suse.lists.egcs-patches>
2002-04-14 15:18 ` Andi Kleen
2002-04-14 15:29 ` Kevin Handy
2002-04-14 23:24 ` Zack Weinberg
2002-04-15 1:21 ` Andi Kleen
2002-04-15 6:35 ` Paul Koning
2002-04-15 7:46 ` Mark Mitchell
2002-04-15 8:07 ` David S. Miller
2002-04-15 8:16 ` Mark Mitchell
2002-04-15 12:59 ` mike stump
2002-04-15 13:23 ` Mark Mitchell
2002-04-16 2:37 ` Hans-Peter Nilsson
2002-04-16 22:40 ` David O'Brien
2002-04-15 10:45 ` Daniel Egger
2002-04-15 12:21 ` Hans-Peter Nilsson
2002-04-15 11:56 ` Hans-Peter Nilsson
2002-04-15 16:49 ` Richard Henderson
2002-04-15 8:20 ` Lars Brinkhoff
2002-04-15 8:33 ` Alan Lehotsky
2002-04-15 10:06 ` Zack Weinberg
2002-04-15 10:42 ` Mark Mitchell
2002-04-15 12:47 ` Janis Johnson
2002-04-25 16:56 ` Jason Merrill
2002-04-15 18:50 ` Stan Shebs
2002-04-16 9:39 ` Zack Weinberg
2002-04-16 9:59 ` Kaveh R. Ghazi
2002-04-18 9:29 ` Kai Henningsen
2002-04-18 10:13 ` Paul Koning
2002-04-19 12:36 ` Hans-Peter Nilsson
2002-04-15 12:50 ` mike stump
2002-04-15 19:31 ` Phil Edwards
2002-04-15 19:46 ` DJ Delorie
2002-04-15 20:08 ` Phil Edwards
2002-04-15 23:06 ` DJ Delorie
2002-04-16 7:01 ` Paul Koning
2002-04-15 23:24 ` Neil Booth
2002-04-16 6:08 ` Phil Edwards
2002-04-17 18:13 ` Zack Weinberg
2002-04-17 19:10 ` DJ Delorie
2002-04-17 20:26 ` Phil Edwards
2002-04-19 12:46 ` Hans-Peter Nilsson
2002-04-15 0:31 ` Zack Weinberg
2002-04-15 17:43 ` Stan Shebs
2002-04-15 17:07 ` David O'Brien
2002-04-16 0:44 ` Douglas B. Rupp
2002-04-16 4:32 ` Joel Sherrill
2002-04-16 7:08 ` Paul Koning
2002-04-16 7:22 ` Joel Sherrill
2002-04-16 3:41 ` Richard Earnshaw
2002-04-16 6:30 ` Nick Burrett
2002-04-15 13:03 Robert Dewar
2002-04-15 9:28 Richard Kenner
2002-04-15 8:13 Robert Dewar
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=C41D82BF5BACD311B1B600A0C9EAF0CF0659BEF2@es01-bos \
--to=eric_dana@bmc.com \
--cc=gcc@gcc.gnu.org \
--cc=matzmich@cs.tu-berlin.de \
/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).