public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/61871] FAIL: regexp from libgo testsuite on non-split stack targets
Date: Tue, 05 Aug 2014 14:31:00 -0000 [thread overview]
Message-ID: <bug-61871-4-tjMh0ED28N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61871-4@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 3301 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61871
--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
Ops, I was also testing with this patch:
--cut here--
Index: go/regexp/all_test.go
===================================================================
--- go/regexp/all_test.go (revision 213529)
+++ go/regexp/all_test.go (working copy)
@@ -475,7 +475,7 @@
// This ran out of stack before issue 7608 was fixed.
func TestOnePassCutoff(t *testing.T) {
- MustCompile(`^(?:x{1,1000}){1,1000}$`)
+ MustCompile(`^(?:x{1,1000}){1,500}$`)
}
func BenchmarkLiteral(b *testing.B) {
--cut here--
>From gcc-bugs-return-457807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Aug 05 14:46:43 2014
Return-Path: <gcc-bugs-return-457807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15691 invoked by alias); 5 Aug 2014 14:46:43 -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 15637 invoked by uid 48); 5 Aug 2014 14:46:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/62025] New: [4.9/4.10 Regression] Miscompilation of openssl sha512.c
Date: Tue, 05 Aug 2014 14:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc cf_gcctarget attachments.created
Message-ID: <bug-62025-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: 2014-08/txt/msg00304.txt.bz2
Content-length: 824
https://gcc.gnu.org/bugzilla/show_bug.cgi?idb025
Bug ID: 62025
Summary: [4.9/4.10 Regression] Miscompilation of openssl
sha512.c
Product: gcc
Version: 4.9.1
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
CC: krebbel at gcc dot gnu.org, rsandifo at gcc dot gnu.org
Target: s390-linux
Created attachment 33248
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id3248&actioníit
sha.c
The following testcase is miscompiled on s390-linux, starting with r207605
(including latest trunk), with e.g. -O2 -m31 -march=z196 -mtune=z10 options.
next parent reply other threads:[~2014-08-05 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-61871-4@http.gcc.gnu.org/bugzilla/>
2014-08-05 14:31 ` ubizjak at gmail dot com [this message]
2014-08-07 11:58 ` ubizjak at gmail dot com
2014-08-07 12:13 ` ubizjak at gmail dot com
2014-08-07 13:38 ` ubizjak at gmail dot com
2014-11-16 11:54 ` ubizjak at gmail dot com
2015-01-05 16:13 ` ian at gcc dot gnu.org
2015-01-05 23:16 ` ubizjak at gmail 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=bug-61871-4-tjMh0ED28N@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).