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/59431] [4.9 regression] runtime FAILs on Solaris Date: Fri, 10 Jan 2014 07:38:00 -0000 [thread overview] Message-ID: <bug-59431-4-N7DcJ45Cw7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59431-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59431 --- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> --- This should now be fixed by [1]. [1] http://gcc.gnu.org/ml/gcc-patches/2014-01/msg00565.html >From gcc-bugs-return-439900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 10 08:33:44 2014 Return-Path: <gcc-bugs-return-439900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18382 invoked by alias); 10 Jan 2014 08:33: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 18330 invoked by uid 55); 10 Jan 2014 08:33:39 -0000 From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/59723] [4.9 Regression] ICE: in lto_output_tree, at lto-streamer-out.c:1390 when compiling some Fortran tests with -flto Date: Fri, 10 Jan 2014 08:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59723-4-UxGQK1MOl9@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59723-4@http.gcc.gnu.org/bugzilla/> References: <bug-59723-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-01/txt/msg01042.txt.bz2 Content-length: 862 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY723 --- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> --- On Thu, 9 Jan 2014, dominiq at lps dot ens.fr wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?idY723 > > --- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > > ... which implies that the GCC testsuite needs to be improved with regards > > to LTO testing as there was no new failure with the patch. Maybe ... but if you modify LTO code for a feature I'd expect you try LTO on a simple example using that feature ;) > Not GCC, but gfortran. I stumbled on this pr with > > make -k check-gfortran > RUNTESTFLAGS="--target_board=unix'{-m32/-flto,-m64/-flto}'" > > One may consider to add something '-Ofast -flto' to the set of options in > gfortran.dg. One always has to weight in testing time of course.
next prev parent reply other threads:[~2014-01-10 7:38 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-09 15:33 [Bug go/59431] New: " ro at gcc dot gnu.org 2013-12-09 15:34 ` [Bug go/59431] " ro at gcc dot gnu.org 2013-12-17 18:31 ` jakub at gcc dot gnu.org 2014-01-10 7:38 ` ubizjak at gmail dot com [this message] 2014-01-10 9:42 ` ro at CeBiTec dot Uni-Bielefeld.DE 2014-01-10 17:04 ` ian at airs dot com 2014-02-20 13:36 ` ro at CeBiTec dot Uni-Bielefeld.DE 2014-04-22 11:38 ` [Bug go/59431] [4.9/4.10 " jakub at gcc dot gnu.org 2014-07-16 13:31 ` jakub at gcc dot gnu.org 2014-10-30 11:29 ` [Bug go/59431] [4.9/5 " jakub at gcc dot gnu.org 2015-06-26 20:18 ` [Bug go/59431] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:39 ` jakub at gcc dot gnu.org 2021-05-14 9:47 ` [Bug go/59431] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:06 ` rguenth at gcc dot gnu.org 2022-05-27 9:35 ` [Bug go/59431] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:30 ` jakub at gcc dot gnu.org 2023-07-07 10:30 ` [Bug go/59431] [11/12/13/14 " rguenth 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-59431-4-N7DcJ45Cw7@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: linkBe 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).