public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Momchil Velikov <velco@fadata.bg> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/3218: ARM/Thumb: Illegal byte-oriented stack instructions Date: Tue, 22 Jan 2002 03:26:00 -0000 [thread overview] Message-ID: <20020122112602.27678.qmail@sources.redhat.com> (raw) The following reply was made to PR target/3218; it has been noted by GNATS. From: Momchil Velikov <velco@fadata.bg> To: pb@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, trauscher@loytec.com, gcc-gnats@gcc.gnu.org Subject: Re: target/3218: ARM/Thumb: Illegal byte-oriented stack instructions Date: 22 Jan 2002 13:23:17 +0200 >>>>> "pb" == pb <pb@gcc.gnu.org> writes: pb> Synopsis: ARM/Thumb: Illegal byte-oriented stack instructions pb> State-Changed-From-To: open->analyzed pb> State-Changed-By: pb pb> State-Changed-When: Tue Jan 22 03:12:10 2002 pb> State-Changed-Why: pb> Bug still exists with current 3.0 sources pb> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3218 The thread starting here is relevent to this PR. http://gcc.gnu.org/ml/gcc-patches/2002-01/msg01263.html
next reply other threads:[~2002-01-22 11:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-22 3:26 Momchil Velikov [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-30 5:08 rearnsha 2002-01-22 3:12 pb 2001-06-18 1:16 trauscher
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=20020122112602.27678.qmail@sources.redhat.com \ --to=velco@fadata.bg \ --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).