public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bjoern dot m dot haase at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/21078] New: Testsuite reports excecution failure for gcc.c-torture/excecute/20010122.c for some optimization levels
Date: Sun, 17 Apr 2005 22:32:00 -0000	[thread overview]
Message-ID: <20050417223234.21078.bjoern.m.haase@web.de> (raw)

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

Test case gcc.c-torture/excecute/20010122-1.c fails the execution tests for 
optimization levels -O1, -O2, -O3-g and -Os while passing for -O0. Tests were 
run with simulavr for the atmega128. 
 
I do not have a clear opinion about what is going wrong. The fact that the test 
passes for -O0 is reason for being suspicious, however. 
 
Yours, 
 
Björn

-- 
           Summary: Testsuite reports excecution failure for gcc.c-
                    torture/excecute/20010122.c for some optimization levels
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bjoern dot m dot haase at web dot de
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i586-linux
  GCC host triplet: i586-linux
GCC target triplet: avr-*-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21078


             reply	other threads:[~2005-04-17 22:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17 22:32 bjoern dot m dot haase at web dot de [this message]
2005-04-17 22:41 ` [Bug target/21078] " pinskia at gcc dot gnu dot org
2005-04-17 22:47 ` pinskia at gcc dot gnu dot org
2005-04-19 15:47 ` ericw at evcohs dot com

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=20050417223234.21078.bjoern.m.haase@web.de \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).