public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: grubba@roxen.com
To: gcc-gnats@gcc.gnu.org
Cc: grubba@roxen.com
Subject: c/2386: gcc -mcpu=ultrasparc SIGSEGV's on some code involving long long and pointers.
Date: Sun, 25 Mar 2001 12:46:00 -0000	[thread overview]
Message-ID: <20010325203706.2173.qmail@sourceware.cygnus.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]

>Number:         2386
>Category:       c
>Synopsis:       gcc -mcpu=ultrasparc SIGSEGV's on some code involving long long and pointers.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Mar 25 12:46:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Henrik Grubbström <grubba@roxen.com>
>Release:        gcc version 2.95.2 19991024 (release)
>Organization:
>Environment:
$ uname -svrmpi
SunOS 5.8 Generic_108528-04 sun4u sparc SUNW,Ultra-80
>Description:
gcc dies with SIGSEGV when compiling the attached file with -mcpu=ultrasparc.
>How-To-Repeat:
$ gcc -mcpu=ultrasparc -c foo.c -o foo.o
gcc: Internal compiler error: program cc1 got fatal signal 11
>Fix:
Rewriting the subtraction as:
	stack_top -= lim.rlim_cur;
seems to work around the bug.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-c-code; name="foo.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="foo.c"

CnR5cGVkZWYJdW5zaWduZWQgbG9uZyBsb25nCXVfbG9uZ2xvbmdfdDsKdHlwZWRlZiB1X2xvbmds
b25nX3QJcmxpbTY0X3Q7CnN0cnVjdCBybGltaXQ2NCB7CglybGltNjRfdAlybGltX2N1cjsJIAoJ
cmxpbTY0X3QJcmxpbV9tYXg7CSAKfTsKZXh0ZXJuIGludCBnZXRybGltaXQ2NCAoaW50LCBzdHJ1
Y3QgcmxpbWl0NjQgICopOwpleHRlcm4gY2hhciAqc3RhY2tfdG9wOwppbnQgbWFpbiAoaW50IGFy
Z2MsIGNoYXIgKiphcmd2KQp7CiAgewogICAgc3RydWN0IHJsaW1pdDY0ICBsaW07CiAgICBpZigh
IGdldHJsaW1pdDY0ICgzICwgJmxpbSkpCiAgICB7CiAgICAgIHN0YWNrX3RvcCArPSAtMSAgKiBs
aW0ucmxpbV9jdXI7CiAgICB9CiAgfQp9Cg==


                 reply	other threads:[~2001-03-25 12:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010325203706.2173.qmail@sourceware.cygnus.com \
    --to=grubba@roxen.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).