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 18:36:00 -0000 [thread overview] Message-ID: <20020115023611.14034.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, 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 18:32:43 -0800 (PST) I did spend some time trying to provide a short test case but was unable to. And in fact i have not seen this bug anywhere else but from this one fairly complicated source file. I worked around the problem by a adding in a local variable instead of working directly off of an element of an auto array. (The fact that i haven't seen this problem again is probably due largely to the fact that we generally avoid auto arrays due to small stack sizes... so maybe it isn't such an obscure corner after all.) I can send you the .i (preprocessed) file and the resulting .s file (and the error messages) but i have to have some assurance of privacy (not a guarantee) since the files could be considered sensitive (although they are hardly the company's crown jewels). I.e. i can't post it in the bug database. Thanks Ted Merrill On 14 Jan 2002 rodrigc@gcc.gnu.org wrote: > Old Synopsis: gcc 3.0, ARM/thumb target, generates invalid asm > New Synopsis: [ARM] gcc 3.0, ARM/thumb target, generates invalid asm > > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Sun Jan 13 16:35:02 2002 > State-Changed-Why: > Can you provide a test-case? > If you want to contact Richard Earnshaw directly, his > e-mail address is in the gcc/MAINTAINERS file > in the gcc distribution. > > Do you still want to keep this PR open? > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4508 >
next reply other threads:[~2002-01-15 2:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-14 18:36 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 19:46 Ted Merrill 2002-01-14 18:48 rodrigc 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=20020115023611.14034.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).