public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com
To: gcc-gnats@gcc.gnu.org
Subject: c/6277: Failure of test gcc.dg/i386-387-1.c on cygwin
Date: Fri, 12 Apr 2002 07:36:00 -0000	[thread overview]
Message-ID: <20020412143429.30236.qmail@sources.redhat.com> (raw)


>Number:         6277
>Category:       c
>Synopsis:       Failure of test gcc.dg/i386-387-1.c on cygwin
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 12 07:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     David Billinghurst
>Release:        unknown-1.0
>Organization:
>Environment:
i686-pc-cygwin
>Description:
gcc.dg/i386-387-1.c fails on cygwin with:

FAIL: gcc.dg/i386-387-1.c scan-assembler call	sin
FAIL: gcc.dg/i386-387-1.c scan-assembler call	cos
FAIL: gcc.dg/i386-387-1.c scan-assembler call	sqrt

Inspection of the assembler shows lines "call  _sin" etc
If this is the desired outcome then the scan-assembler
regex needs patching (below)
>How-To-Repeat:
bootstrap and run testsuite
>Fix:
Index: i386-387-1.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/testsuite/gcc.dg/i386-387-1.c,v
retrieving revision 1.1.2.1
diff -u -r1.1.2.1 i386-387-1.c
--- i386-387-1.c        29 Mar 2002 23:21:41 -0000      1.1.2.1
+++ i386-387-1.c        12 Apr 2002 14:33:42 -0000
@@ -1,9 +1,9 @@
 /* Verify that -mno-fancy-math-387 works.  */
 /* { dg-do compile { target "i?86-*-*" } } */
 /* { dg-options "-O -ffast-math -mfpmath=387 -mno-fancy-math-387" } */
-/* { dg-final { scan-assembler "call\tsin" } } */
-/* { dg-final { scan-assembler "call\tcos" } } */
-/* { dg-final { scan-assembler "call\tsqrt" } } */
+/* { dg-final { scan-assembler "call\t_?sin" } } */
+/* { dg-final { scan-assembler "call\t_?cos" } } */
+/* { dg-final { scan-assembler "call\t_?sqrt" } } */

 double f1(double x) { return __builtin_sin(x); }
 double f2(double x) { return __builtin_cos(x); }
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="i386-387-1.s"
Content-Disposition: inline; filename="i386-387-1.s"

	.file	"i386-387-1.c"
	.text
	.align 2
.globl _f1
	.def	_f1;	.scl	2;	.type	32;	.endef
_f1:
	pushl	%ebp
	movl	%esp, %ebp
	subl	$8, %esp
	movl	8(%ebp), %eax
	movl	12(%ebp), %edx
	movl	%eax, (%esp)
	movl	%edx, 4(%esp)
	call	_sin
	movl	%ebp, %esp
	popl	%ebp
	ret
	.align 2
.globl _f2
	.def	_f2;	.scl	2;	.type	32;	.endef
_f2:
	pushl	%ebp
	movl	%esp, %ebp
	subl	$8, %esp
	movl	8(%ebp), %eax
	movl	12(%ebp), %edx
	movl	%eax, (%esp)
	movl	%edx, 4(%esp)
	call	_cos
	movl	%ebp, %esp
	popl	%ebp
	ret
	.align 2
.globl _f3
	.def	_f3;	.scl	2;	.type	32;	.endef
_f3:
	pushl	%ebp
	movl	%esp, %ebp
	subl	$8, %esp
	movl	8(%ebp), %eax
	movl	12(%ebp), %edx
	movl	%eax, (%esp)
	movl	%edx, 4(%esp)
	call	_sqrt
	movl	%ebp, %esp
	popl	%ebp
	ret
	.def	_sqrt;	.scl	2;	.type	32;	.endef
	.def	_cos;	.scl	2;	.type	32;	.endef
	.def	_sin;	.scl	2;	.type	32;	.endef


             reply	other threads:[~2002-04-12 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12  7:36 David.Billinghurst [this message]
2002-04-14  4:54 billingd

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=20020412143429.30236.qmail@sources.redhat.com \
    --to=david.billinghurst@riotinto.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).