public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] mesa 11.0.9-2 [GOLDSTAR]
Date: Thu, 09 Jun 2016 22:01:00 -0000	[thread overview]
Message-ID: <e9bd250e-783d-0ce0-f1ee-e9614e5d8c17@cygwin.com> (raw)
In-Reply-To: <755f21b3-98aa-9283-0054-369bdb1657a0@dronecode.org.uk>

On 6/6/2016 9:27 AM, Jon Turney wrote:
> On 06/06/2016 08:24, Yaakov Selkowitz wrote:
>> On 2016-06-03 12:56, Jon Turney wrote:
>>> On 31/05/2016 18:03, Jon Turney wrote:
>>>>> # gdb ./quad-clip
>>>>> [...]
>>>>> (gdb) r
>>>>> [...]
>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>> 0x7fdf00c1 in ?? ()
>>> [...]
>>>>> /usr/src/debug/mesa-demos-8.3.0-1/src/trivial/quad-clip.c:137
>>>>> (gdb) disassemble 0x7fdf00b1,0x7fdf00d2
>>>>> Dump of assembler code from 0x7fdf00b1 to 0x7fdf00d2:
>>>>>    0x7fdf00b1:  insertps $0x10,0x4(%eax,%edi,1),%xmm0
>>>>>    0x7fdf00b9:  insertps $0x20,0x8(%eax,%edi,1),%xmm0
>>>>> => 0x7fdf00c1:  insertps $0x30,0xfffeff34,%xmm0
>>>>>    0x7fdf00cb:  mov    (%esi),%eax
>>>>>    0x7fdf00cd:  mul    %ecx
>>>
>>> After staring this a bit more, I see that this is the offset to the data
>>> to load, apparently being used as an absolute address
>>>
>>> This seems to be the case with other addresses in the JIT-ed code,  so
>>> perhaps there is some problem preventing relocations being applied...
>>
>> FWIW, I tried rebuilding with llvm 3.8.0.  32-bit doesn't crash anymore,
>> and glxgears says its running, but only the background shows.
>
> Thanks, that was next on my list to try
>
> That sounds exactly like what I see with llvm svn r251761 [1] backported
> to 3.7.1 (without which we use the x86_64 loader on x86, rather than
> reporting an error, due to an interesting use of __builtin_undefined,
> with hilarious consequences)
>
> I guess the output of the JIT code is ending up the wrong place as well,
> or something...

For the record, Jon seems to have tracked this down, and his fix is in 
llvm-3.7.1-2.  I can only imagine what "fun" he had debugging this, 
particularly on the address-starved 32-bit platform.

Andrew, could you please do the honours?

-- 
Yaakov

--
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:[~2016-06-09 22:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22  9:08 [ANNOUNCEMENT] mesa 11.0.9-2 Yaakov Selkowitz
2016-04-12 15:20 ` Marco Atzeri
2016-04-13  2:17   ` gdb using Windows paths in dlopen()ed modules? Yaakov Selkowitz
2016-04-13  8:09     ` Corinna Vinschen
2016-04-13  2:33   ` [ANNOUNCEMENT] mesa 11.0.9-2 Yaakov Selkowitz
2016-05-25 13:56     ` Marco Atzeri
     [not found]     ` <b8ee7d32-504d-27d8-51ab-547ea7a51968@dronecode.org.uk>
2016-06-03 17:56       ` Jon Turney
2016-06-06  7:25         ` Yaakov Selkowitz
2016-06-06 14:27           ` Jon Turney
2016-06-09 22:01             ` Yaakov Selkowitz [this message]
2016-06-10  4:36               ` [ANNOUNCEMENT] mesa 11.0.9-2 [GOLDSTAR] Marco Atzeri
2016-06-10  8:31                 ` Corinna Vinschen
2016-06-10 14:49               ` Andrew Schulman
2016-06-20 18:29               ` Jon Turney

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=e9bd250e-783d-0ce0-f1ee-e9614e5d8c17@cygwin.com \
    --to=yselkowitz@cygwin.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).