public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Ted Merrill <ted@arraycomm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/4508: [ARM] gcc 3.0, ARM/thumb target, generates invalid asm Date: Mon, 14 Jan 2002 19:46:00 -0000 [thread overview] Message-ID: <20020115034602.26587.qmail@sources.redhat.com> (raw) The following reply was made to PR target/4508; it has been noted by GNATS. From: Ted Merrill <ted@arraycomm.com> To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rodrigc@gcc.gnu.org, ted@arraycomm.com, rearnsha@arm.com, gcc-gnats@gcc.gnu.org Cc: Subject: Re: target/4508: [ARM] gcc 3.0, ARM/thumb target, generates invalid asm Date: Mon, 14 Jan 2002 19:45:03 -0800 (PST) I don't need support (at least not at this time), i was just trying to improve the compiler. The MAINTAINERS file doesn't say who is the maintainer for ARM but does still list Richard Earnshaw. Since he hasn't commented on this bug, perhaps he is no longer the maintainer? I'm copying him anyway, but i think past attempts to communicate to him directly have not succeeded. Thanks Ted Merrill On 15 Jan 2002 rodrigc@gcc.gnu.org wrote: > Synopsis: [ARM] gcc 3.0, ARM/thumb target, generates invalid asm > > State-Changed-From-To: feedback->suspended > State-Changed-By: rodrigc > State-Changed-When: Mon Jan 14 18:48:18 2002 > State-Changed-Why: > The FSF gcc project cannot really help you > if you cannot provide a test-case, and > cannot guarantee privacy. > > You can contact the gcc ARM maintainer directly, > or perhaps contract someone who supports gcc commercially > if you require additional support. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4508 >
next reply other threads:[~2002-01-15 3:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-14 19:46 Ted Merrill [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-10 22:06 wb 2002-01-15 13:28 rodrigc 2002-01-15 13:06 Ted Merrill 2002-01-15 2:36 Richard Earnshaw 2002-01-14 18:48 rodrigc 2002-01-14 18:36 Ted Merrill 2002-01-13 16:35 rodrigc
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=20020115034602.26587.qmail@sources.redhat.com \ --to=ted@arraycomm.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: linkBe 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).