public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Raimar Falke <rf13@inf.tu-dresden.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8439: using an empty struct causes Internal compiler error in instantiate_virtual_regs_1, at function.c:4126
Date: Mon, 04 Nov 2002 11:26:00 -0000	[thread overview]
Message-ID: <20021104192600.25679.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/8439; it has been noted by GNATS.

From: Raimar Falke <rf13@inf.tu-dresden.de>
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c/8439: using an empty struct causes Internal compiler error in instantiate_virtual_regs_1, at function.c:4126
Date: Mon, 4 Nov 2002 20:18:07 +0100

 On Sun, Nov 03, 2002 at 06:26:00PM -0000, gcc-gnats@gcc.gnu.org wrote:
 > Thank you very much for your problem report.
 > It has the internal identification `c/8439'.
 > The individual assigned to look at your
 > report is: unassigned. 
 
 The problem is non-reproducible on a sun:
 
 $ uname -a
 SunOS irz601 5.7 Generic_106541-22 sun4u sparc SUNW,Ultra-2
 $ gcc --version
 gcc (GCC) 3.2
 Copyright (C) 2002 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 
 $ gcc -c c.c
 $ gcc -c -S c.c
 $ cat c.s
    .file   "c.c"
         .section        ".text"
         .align 4
         .type   foobar,#function
         .proc   020
 foobar:
         !#PROLOGUE# 0
         save    %sp, -112, %sp
         !#PROLOGUE# 1
         st      %i0, [%fp+68]
         ld      [%fp+68], %i0
         add     %i0, 0, %i0
         st      %i0, [%fp+68]
         nop
         ret
         restore
 .LLfe1:
         .size   foobar,.LLfe1-foobar
         .ident  "GCC: (GNU) 3.2"
 $
 
 	Raimar
 
 -- 
  email: rf13@inf.tu-dresden.de
  "The very concept of PNP is a lovely dream that simply does not translate to
   reality. The confusion of manually doing stuff is nothing compared to the
   confusion of computers trying to do stuff and getting it wrong, which they
   gleefully do with great enthusiasm." 
     -- Jinx Tigr in the SDM


             reply	other threads:[~2002-11-04 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 11:26 Raimar Falke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-03 10:31 paolo
2002-11-03 10:26 rf13

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=20021104192600.25679.qmail@sources.redhat.com \
    --to=rf13@inf.tu-dresden.de \
    --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: 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).