public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/65665] [5.0 Regression]: g++.dg/torture/pr64378.C   -O2 -flto -fno-use-linker-plugin -flto-partition=none
Date: Fri, 03 Apr 2015 08:46:00 -0000	[thread overview]
Message-ID: <bug-65665-4-8FSnq4lPs3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65665-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65665

--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Hello.

I've just sent patch to mailing list:
https://gcc.gnu.org/ml/gcc-patches/2015-04/msg00108.html

May I ask you for testing if it survives on your target?

Thanks,
Martin
>From gcc-bugs-return-482640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 03 08:46:29 2015
Return-Path: <gcc-bugs-return-482640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28986 invoked by alias); 3 Apr 2015 08:46:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28896 invoked by uid 48); 3 Apr 2015 08:46:21 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/65205] Wrong dg-shouldfail usage in OpenACC libgomp tests
Date: Fri, 03 Apr 2015 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: major
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jnorris at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-65205-4-G9pZ6LLsG2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65205-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65205-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg00192.txt.bz2
Content-length: 820

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide205

vries at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-04-03
     Ever confirmed|0                           |1

--- Comment #1 from vries at gcc dot gnu.org ---
Confirmed. I see during testing in /var/log/kern.log:
...
Apr  3 10:30:34 linux1 kernel: [40550.740064] lib-42.exe[1885]: segfault at 0
ip 00002b359109463e sp 00007fffd2ec80a0 error 4 in
libgomp.so.1.0.0[2b359107d000+20000]
...

And the failure mode we expect is:
...
/* { dg-shouldfail "libgomp: \[\h+,256\] is not mapped" } */
...

So the dg-shouldfail is currently hiding a problem.


  parent reply	other threads:[~2015-04-03  8:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03  0:55 [Bug middle-end/65665] New: " hp at gcc dot gnu.org
2015-04-03  1:05 ` [Bug middle-end/65665] " hp at gcc dot gnu.org
2015-04-03  8:41 ` dominiq at lps dot ens.fr
2015-04-03  8:46 ` marxin at gcc dot gnu.org [this message]
2015-04-03  8:56 ` dominiq at lps dot ens.fr
2015-04-03 13:07 ` hp at gcc dot gnu.org
2015-04-03 14:22 ` dominiq at lps dot ens.fr
2015-04-03 14:47 ` dominiq at lps dot ens.fr
2015-04-04 12:05 ` hp at gcc dot gnu.org
2015-04-05 17:18 ` marxin at gcc dot gnu.org

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=bug-65665-4-8FSnq4lPs3@http.gcc.gnu.org/bugzilla/ \
    --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).