public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jim Wilson <wilson@redhat.com>
To: gcc-gnats@gcc.gnu.org
Subject: middle-end/6600: i960 toolchain hits abort in c_readstr
Date: Tue, 07 May 2002 14:36:00 -0000	[thread overview]
Message-ID: <200205072128.g47LSgC31097@tonopah.toronto.redhat.com> (raw)


>Number:         6600
>Category:       middle-end
>Synopsis:       i960 toolchain hits abort in c_readstr
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Tue May 07 14:36:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        3.2 20020426 (experimental)
>Organization:
Red Hat
>Environment:
System: Linux tonopah.toronto.redhat.com 2.4.9-31smp #1 SMP Tue Feb 26 06:55:00 EST 2002 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i960-unknown-coff
configured with: ../src/configure --target=i960-coff
>Description:
	If you have a program that calls strcpy/memcpy with a constant string
	of 16 bytes or more, and you compile with optimization, then gcc aborts
	in c_readstr in builtins.c.

	The i960 toolchain has instructions to move 16 bytes (4 registers) at
	a time.  Constant strings get 16 byte alignment so that we can use
	these instructions.  strcpy/memcpy are trying to optimize calls with
	a constant string as a parameter.  Unfortunately, you can only put 8
	bytes at a time in a CONST_DOUBLE, so c_readstr aborts when asked to
	convert 16 bytes of string into a single RTL constant.
>How-To-Repeat:
	Compile gcc.c-torture/execute/20000703-1.c with -O for an i960-coff
	target.
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-07 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 14:36 Jim Wilson [this message]
2002-05-16 12:31 sayle
2002-05-23 21:27 sayle

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=200205072128.g47LSgC31097@tonopah.toronto.redhat.com \
    --to=wilson@redhat.com \
    --cc=gcc-gnats@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).