public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65894] [6 Regression] severe regression in gfortran 6.0.0 Date: Tue, 28 Apr 2015 11:59:00 -0000 [thread overview] Message-ID: <bug-65894-4-Ai6SpiTvzZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65894-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65894 --- Comment #10 from Jürgen Reuter <juergen.reuter at desy dot de> --- (In reply to Dominique d'Humieres from comment #9) > > With the attached patch your small test case and the test suite runs > > w/o segfault now. Furthermore does gcc6 bootstrap and regtest ok > > with the patch. > > Confirmed. The bigger test in comment 2 runs without segfault also. However > I get an ICE when compiling the full package at > http://whizard.hepforge.org/versions/unofficial/whizard-2.2.6_alpha-20150426. > tar.gz > > libtool: compile: gfc -I../basics -I../utilities -I../testing -I../system > -I../combinatorics -I../expr_base -I../physics -g -O2 -c evaluators.f90 > -fno-common -o .libs/evaluators.o > evaluators.f90:897:0: > > .or. qn_mask_rest > 1 > internal compiler error: in gfc_trans_assignment_1, at > fortran/trans-expr.c:9203 I confirm this ICE with the patch and will provide a smaller test case soon. >From gcc-bugs-return-484838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Apr 28 12:17:26 2015 Return-Path: <gcc-bugs-return-484838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 33287 invoked by alias); 28 Apr 2015 12:17:26 -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 33245 invoked by uid 48); 28 Apr 2015 12:17:22 -0000 From: "paul at xk7 dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/62097] mipsel-sde-elf build fails on OS X 10.7 host Date: Tue, 28 Apr 2015 12:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Version: 4.9.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: paul at xk7 dot net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: cc Message-ID: <bug-62097-4-DyhEh7UukU@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-62097-4@http.gcc.gnu.org/bugzilla/> References: <bug-62097-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/msg02390.txt.bz2 Content-length: 711 https://gcc.gnu.org/bugzilla/show_bug.cgi?idb097 Paul Waring <paul at xk7 dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paul at xk7 dot net --- Comment #3 from Paul Waring <paul at xk7 dot net> --- I can confirm the same issue occurs for me on OS X 10.10 (Yosemite) and the following: GCC: 4.9.2 binutils: 2.25 MPFR: 3.1.2 MPC: 1.0.3 GMP: 6.0.0a Newlib: 2.2.0-1 clang --version Apple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM 3.6.0svn) Target: x86_64-apple-darwin14.3.0 Thread model: posix Is there anything I can do to help fix this bug?
next prev parent reply other threads:[~2015-04-28 11:59 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-26 14:35 [Bug fortran/65894] New: " juergen.reuter at desy dot de 2015-04-26 15:02 ` [Bug fortran/65894] " juergen.reuter at desy dot de 2015-04-27 9:20 ` [Bug fortran/65894] [6 Regression] " rguenth at gcc dot gnu.org 2015-04-27 9:27 ` vehre at gcc dot gnu.org 2015-04-27 9:40 ` juergen.reuter at desy dot de 2015-04-27 9:41 ` juergen.reuter at desy dot de 2015-04-27 16:56 ` vehre at gcc dot gnu.org 2015-04-28 6:33 ` dominiq at lps dot ens.fr 2015-04-28 11:59 ` juergen.reuter at desy dot de [this message] 2015-04-28 16:10 ` juergen.reuter at desy dot de 2015-05-05 17:12 ` vehre at gcc dot gnu.org 2015-05-05 17:35 ` juergen.reuter at desy dot de 2015-05-05 18:06 ` vehre at gcc dot gnu.org 2015-05-06 6:54 ` dominiq at lps dot ens.fr 2015-05-07 9:54 ` vehre at gcc dot gnu.org 2015-05-07 9:57 ` juergen.reuter at desy dot de 2015-05-07 10:09 ` vehre at gcc dot gnu.org 2015-05-07 10:14 ` juergen.reuter at desy dot de 2015-05-07 12:10 ` juergen.reuter at desy dot de 2015-05-07 12:20 ` dominiq at lps dot ens.fr 2015-05-07 12:22 ` juergen.reuter at desy dot de 2015-05-07 12:38 ` juergen.reuter at desy dot de 2015-05-07 19:27 ` dominiq at lps dot ens.fr 2015-05-07 20:46 ` dominiq at lps dot ens.fr 2015-05-08 5:36 ` juergen.reuter at desy dot de 2015-05-08 12:47 ` dominiq at lps dot ens.fr 2015-05-08 18:53 ` dominiq at lps dot ens.fr 2015-05-09 13:36 ` mikael at gcc dot gnu.org 2015-05-10 13:40 ` mikael 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-65894-4-Ai6SpiTvzZ@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).