public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/63622] [5.0 Regression] Bootstrap fails on x86_64-apple-darwin1[34] after revision r216305
Date: Tue, 11 Nov 2014 17:11:00 -0000	[thread overview]
Message-ID: <bug-63622-4-oGpyOGYO4A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63622-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #29 from howarth at bromo dot med.uc.edu ---
(In reply to howarth from comment #28)
> At r217355, the failures for the gfortran.dg/assumed_rank_[8/9/10].f90
> execution tests , first noted in Comment 7, still remain on x86_64 darwin.

A backtrace of the failing test case generated by...

/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/testsuite/gfortran/../../gfortran
-B/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/testsuite/gfortran/../../
-B/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/i386/libgfortran/
/sw/src/fink.build/gcc50-5.0.0-1000/gcc-5-20141111/gcc/testsuite/gfortran.dg/assumed_rank_10.f90
-fno-diagnostics-show-caret -fdiagnostics-color=never -O3 -fomit-frame-pointer
-funroll-loops -fdump-tree-original
-B/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/i386/libgfortran/.libs
-L/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/i386/libgfortran/.libs
-L/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/i386/libgfortran/.libs
-B/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/i386/libquadmath/.libs
-L/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/i386/libquadmath/.libs
-L/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/i386/libquadmath/.libs
-lm -m32 -o ./assumed_rank_10.exe

in lldb appears as...

% lldb
/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/testsuite/gfortran/assumed_rank_10.exe
(lldb) target create
"/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/testsuite/gfortran/assumed_rank_10.exe"
Current executable set to
'/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/testsuite/gfortran/assumed_rank_10.exe'
(i386).
(lldb) r
Process 99438 launched:
'/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/testsuite/gfortran/assumed_rank_10.exe'
(i386)

Program aborted. Backtrace:
#0  0x5151
#1  0x6caf
#2  0xbd577
#3  0x1a8f
#4  0x1bfa
Process 99438 stopped
* thread #1: tid = 0x101913c, 0x9ab09952 libsystem_kernel.dylib`__pthread_kill
+ 10, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
    frame #0: 0x9ab09952 libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill + 10:
-> 0x9ab09952:  jae    0x9ab09962                ; __pthread_kill + 26
   0x9ab09954:  calll  0x9ab09959                ; __pthread_kill + 17
   0x9ab09959:  popl   %edx
   0x9ab0995a:  movl   0x6c996c7(%edx), %edx
(lldb) bt
* thread #1: tid = 0x101913c, 0x9ab09952 libsystem_kernel.dylib`__pthread_kill
+ 10, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
  * frame #0: 0x9ab09952 libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x9083c167 libsystem_pthread.dylib`pthread_kill + 101
    frame #2: 0x97beb29c libsystem_c.dylib`abort + 155
    frame #3: 0x00006c90 libgfortran.3.dylib`__gfortrani_sys_abort + 32 at
error.c:180
    frame #4: 0x000bd578 libgfortran.3.dylib`_gfortran_abort + 8 at abort.c:33
    frame #5: 0x00001a90 assumed_rank_10.exe`fpa.3310 + 48
    frame #6: 0x00001bfb assumed_rank_10.exe`main + 283
    frame #7: 0x92e5d701 libdyld.dylib`start + 1
(lldb)


  parent reply	other threads:[~2014-11-11 17:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 20:23 [Bug bootstrap/63622] New: " dominiq at lps dot ens.fr
2014-10-23 11:24 ` [Bug bootstrap/63622] " rguenth at gcc dot gnu.org
2014-10-23 16:21 ` dominiq at lps dot ens.fr
2014-10-29 15:11 ` marxin at gcc dot gnu.org
2014-10-29 22:13 ` dominiq at lps dot ens.fr
2014-10-30  1:03 ` howarth at bromo dot med.uc.edu
2014-10-30 10:07 ` marxin at gcc dot gnu.org
2014-10-30 15:41 ` dominiq at lps dot ens.fr
2014-11-05 22:16 ` howarth at bromo dot med.uc.edu
2014-11-05 22:46 ` howarth at bromo dot med.uc.edu
2014-11-05 23:12 ` howarth at bromo dot med.uc.edu
2014-11-06  1:19 ` howarth at bromo dot med.uc.edu
2014-11-06  1:32 ` howarth at bromo dot med.uc.edu
2014-11-06  3:10 ` redi at gcc dot gnu.org
2014-11-06  3:47 ` howarth at bromo dot med.uc.edu
2014-11-06  3:54 ` howarth at bromo dot med.uc.edu
2014-11-06  4:09 ` howarth at bromo dot med.uc.edu
2014-11-06  4:28 ` howarth at bromo dot med.uc.edu
2014-11-06  8:36 ` izamyatin at gmail dot com
2014-11-06 10:29 ` marxin at gcc dot gnu.org
2014-11-06 15:38 ` howarth at bromo dot med.uc.edu
2014-11-10 21:08 ` iains at gcc dot gnu.org
2014-11-11 17:02 ` howarth at bromo dot med.uc.edu
2014-11-11 17:11 ` howarth at bromo dot med.uc.edu [this message]
2014-11-11 17:14 ` howarth at bromo dot med.uc.edu
2014-11-11 17:17 ` howarth at bromo dot med.uc.edu
2014-11-11 17:57 ` howarth at bromo dot med.uc.edu
2014-11-11 17:58 ` howarth at bromo dot med.uc.edu
2014-11-11 18:07 ` dominiq at lps dot ens.fr
2014-11-11 19:12 ` fxcoudert at gcc dot gnu.org
2014-11-13 16:13 ` dominiq at lps dot ens.fr

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-63622-4-oGpyOGYO4A@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).