public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin at netbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/11965] On SPARC, gcc produces invalid assembler code for a shift << 32 operation
Date: Tue, 19 Aug 2003 20:04:00 -0000	[thread overview]
Message-ID: <20030819200405.7377.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030818124133.11965.jk@tools.de>

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

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


martin at netbsd dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin at netbsd dot org


------- Additional Comments From martin at netbsd dot org  2003-08-19 20:04 -------
Forgot to mention: I used gcc version 3.3.1.
I initially left out the 32bit changes (since that cases currently seem to not
be triggered), but Ian L. Taylor told me you can not rely on that and pointed to
the mips backends way of handling it.


  parent reply	other threads:[~2003-08-19 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-18 12:41 [Bug c/11965] New: " jk at tools dot de
2003-08-18 17:35 ` [Bug c/11965] " falk at debian dot org
2003-08-19 20:04 ` martin at netbsd dot org [this message]
2003-08-23  1:22 ` dhazeghi at yahoo dot com
2003-08-23 14:24 ` [Bug target/11965] [3.3/3.4 Regression] " pinskia at gcc dot gnu dot org
2003-09-09 14:51 ` [Bug target/11965] [3.3/3.4 Regression] " ebotcazou at gcc dot gnu dot org
2003-09-10 12:59 ` cvs-commit at gcc dot gnu dot org
2003-09-10 13:04 ` cvs-commit at gcc dot gnu dot org
2003-09-10 13:05 ` ebotcazou 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=20030819200405.7377.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).