public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jean-Pierre Flori <jpflori@gmail.com>
To: cygwin@cygwin.com
Subject: Re: libtool weirdness (was Re: Broken MPIR 2.6.0 on Cygwin64)
Date: Fri, 21 Jun 2013 18:10:00 -0000	[thread overview]
Message-ID: <kq24o3$tvh$1@ger.gmane.org> (raw)
In-Reply-To: <kq22dq$m2s$1@ger.gmane.org>

Le Fri, 21 Jun 2013 17:27:22 +0000, Jean-Pierre Flori a écrit :

> Le Fri, 21 Jun 2013 17:06:03 +0000, Jean-Pierre Flori a écrit :
> 
>>> I'll also check without assembly optimizations, or lowering gcc
>>> optimization level, etc.
>> So I'm going to try that now.
> If i disable ASM routines by passing MPN_PATH=generic to configure, then
> (in the static setting at least) most tests now pass.

Using the default MPN_PATH I get "x86_64/sandybridge x86_64 generic", the 
first segfault I get is in the first test in the mpn dir: t-addadd_n.c.
GDB points to the loop1() function:

jp@napoleon-7 ~/mpir-2.6.0/tests/mpn
$ gdb t-addadd_n.exe
GNU gdb (GDB) 7.6.50.20130320-cvs
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/
gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-cygwin".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/jp/mpir-2.6.0/tests/mpn/t-addadd_n.exe...done.
(gdb) r
Starting program: /home/jp/mpir-2.6.0/tests/mpn/t-addadd_n.exe
[New Thread 2576.0x9b8]
[New Thread 2576.0x398]

Program received signal SIGSEGV, Segmentation fault.
0x00000001004020ae in loop1 ()
(gdb) bt
#0  0x00000001004020ae in loop1 ()
#1  0x0000000100401fe7 in __gmpn_addadd_n (t=0x1c8fc0, x=<optimized out>,
    y=<optimized out>, z=<optimized out>, n=1) at addadd_n.c:50
#2  0x0000000100425fb6 in main () at t-addadd_n.c:58

apparently coming from add_n.as.
If someone sees something wrong in the asm files, I have no experience 
with them.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-06-21 18:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 22:56 Broken MPIR 2.6.0 on Cygwin64 Jean-Pierre Flori
2013-06-21  8:33 ` Corinna Vinschen
2013-06-21  9:30   ` Corinna Vinschen
2013-06-21  9:43   ` Jean-Pierre Flori
2013-06-21 10:57     ` Corinna Vinschen
2013-06-21 11:35       ` libtool weirdness (was Re: Broken MPIR 2.6.0 on Cygwin64) Corinna Vinschen
2013-06-21 17:00         ` Jean-Pierre Flori
2013-06-21 17:27           ` Jean-Pierre Flori
2013-06-21 17:35             ` Jean-Pierre Flori
2013-06-21 18:10               ` Jean-Pierre Flori [this message]
2013-06-21 22:44                 ` Jean-Pierre Flori
2013-06-21 22:48                   ` Jean-Pierre Flori
2013-06-24  9:20                     ` Corinna Vinschen
2013-06-24  9:19           ` Corinna Vinschen
2013-06-21 18:05         ` Yaakov (Cygwin/X)
2013-06-24  9:22           ` Corinna Vinschen
2013-06-24 11:55             ` Corinna Vinschen
2013-06-24 16:21               ` Yaakov (Cygwin/X)
2013-06-21 13:39       ` Broken MPIR 2.6.0 on Cygwin64 Jean-Pierre Flori
2013-06-24 11:03         ` Corinna Vinschen

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='kq24o3$tvh$1@ger.gmane.org' \
    --to=jpflori@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).