X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:from:date:message-id:subject:to :cc:content-type; q=dns; s=default; b=Y2b5PyZONTcPQ5DZWxJm1xEiVk QI+fzPQQH8MNM6eNoT5Ne9vDpRmeeFWYztAArAOBM9uysTG6YI/P3ipF5vDTMaW8 z0RFH7OERvu3xvvma0WjOq0RYa5DAs0nFEbdOMayVgbalZFEc5YPye3kPS6MdYsY NcYYeOpYvwfDXjig4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:from:date:message-id:subject:to :cc:content-type; s=default; bh=Fyedjv3y6e4Lhj1sVM9+D8R7rM0=; b= rdloSdi9hZJvqUBttmSHTQ48WII1xP6sPwS5a3otO2+lXwVZPli2HErcjOjOUFPg sWLARt/A3O9hb4Kj4XEKiciPKYeKTNYlxZSLPzLulMFnlYRbS7ZHXEnLIdf/OZXS Zflt78x4jsPFbQi9ZGyarp8evaPW2I0kdce6lxZ6nwY= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qg0-f46.google.com X-Received: by 10.140.21.8 with SMTP id 8mr18903736qgk.55.1396390052263; Tue, 01 Apr 2014 15:07:32 -0700 (PDT) MIME-Version: 1.0 From: Jean-Pierre Flori Date: Wed, 2 Apr 2014 00:07:12 +0200 Message-ID: Subject: Possibly wrong address passed to callq asm instruction within MPIR test binaries To: cygwin AT cygwin DOT com Cc: Bill Hart Content-Type: text/plain; charset=UTF-8 Dear all, It's amazing to see how well Cygwin64 is going. Thanks for your hard work. While preparing the new MPIR release, which will be the first one to support Cygwin4, we encountered problems running MPIR testsuite when MPIR was configured to produce a shared lib. That's with latest cygwin/binutils/gcc/g++ from today. It seems that a call to the MPN_ZERO macro, which on my setup is at 0x4ff2746c0 in the shared lib but we get the instruction: callq 0xff2746c0 within the test binary and that yields a nice segfault. Please see https://groups.google.com/d/msg/mpir-devel/KzsxIWhVx8A/EAUoP4ybWOMJ and the few following post for more details. For sure, we don't get what's going on here. Would you have any clue? Might ld decide for some reason to trim the macro address to 4 bytes rather than 8? Best, -- Jean-Pierre Flori -- 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