public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ghazi@caip.rutgers.edu
To: gcc-gnats@gcc.gnu.org
Cc: rth@redhat.com, davem@redhat.com, jakub@redhat.com,
	mark@codesourcery.com
Subject: target/6569: sparc-sun-solaris2.7 C testsuite regression in compile/20011119-2.c
Date: Sun, 05 May 2002 21:56:00 -0000	[thread overview]
Message-ID: <20020506045410.3873.qmail@sources.redhat.com> (raw)


>Number:         6569
>Category:       target
>Synopsis:       sparc-sun-solaris2.7 C testsuite regression in compile/20011119-2.c
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Sun May 05 21:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Kaveh Ghazi
>Release:        gcc version 3.1 20020505 (prerelease)
>Organization:
>Environment:
sparc-sun-solaris2.7 native as/ld
>Description:
Sometime between 4/26 and 4/29, compile/20011119-2.c regressed.  It worked here:

http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg01050.html
http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg01168.html

It fails here:

http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg01165.html
http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg01120.html

When I compile it by hand using today's checkout, I get:

compile/20011119-2.c:1: warning: weak declaration of `foo' after first use results in unspecified behavior
/usr/ccs/bin/as: "/var/tmp//ccrCbkea.s", line 51: error: invalid operand

I've attached the .s output.

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="20011119-2.s"
Content-Disposition: inline; filename="20011119-2.s"

	.file	"20011119-2.c"
	.section	".text"
	.align 4
	.global bar
	.type	bar,#function
	.proc	04
bar:
	!#PROLOGUE# 0
	save	%sp, -112, %sp
	!#PROLOGUE# 1
	call	foo, 0
	 nop
	mov	%o0, %i0
	nop
	ret
	restore
.LLfe1:
	.size	bar,.LLfe1-bar
	.weak	foo
	foo = xxx
	.align 4
	.global baz
	.type	baz,#function
	.proc	04
baz:
	!#PROLOGUE# 0
	save	%sp, -112, %sp
	!#PROLOGUE# 1
	call	foo, 0
	 nop
	mov	%o0, %i0
	nop
	ret
	restore
.LLfe2:
	.size	baz,.LLfe2-baz
	.align 4
	.global xxx
	.type	xxx,#function
	.proc	04
xxx:
	!#PROLOGUE# 0
	save	%sp, -112, %sp
	!#PROLOGUE# 1
	mov	23, %i0
	nop
	ret
	restore
.LLfe3:
	.size	xxx,.LLfe3-xxx
	.weak	foo
	.ident	"GCC: (GNU) 3.1 20020505 (prerelease)"


             reply	other threads:[~2002-05-06  4:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-05 21:56 ghazi [this message]
2002-05-05 23:03 davem
2002-05-06 15:36 Franz Sirl
2002-05-06 15:46 Mark Mitchell
2002-05-07  5:56 Kaveh R. Ghazi
2002-05-07  6:16 Franz Sirl
2002-05-07  7:46 Mark Mitchell
2002-05-07  7:47 mmitchel
2002-05-07  8:36 Franz Sirl
2002-05-08  7:49 mmitchel

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=20020506045410.3873.qmail@sources.redhat.com \
    --to=ghazi@caip.rutgers.edu \
    --cc=davem@redhat.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mark@codesourcery.com \
    --cc=rth@redhat.com \
    /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).