On 2013-05-07 14:59, Rafael Espíndola wrote:
On 1 May 2013 00:26, Rafael Espíndola wrote:
This is now
http://llvm.org/bugs/show_bug.cgi?id=15882
And it got fixed! :-)
It just missed 3.3 branching, but I will make sure it gets ported.
Okay, can the original posters that suffered from the c
On 1 May 2013 00:26, Rafael Espíndola wrote:
> This is now
>
> http://llvm.org/bugs/show_bug.cgi?id=15882
And it got fixed! :-)
It just missed 3.3 branching, but I will make sure it gets ported.
Cheers,
Rafael
___
freebsd-ports@freebsd.org mailing lis
On Tue, Apr 30, 2013 at 11:26 PM, Rafael Espíndola
wrote:
> This is now
>
> http://llvm.org/bugs/show_bug.cgi?id=15882
>
> Someone familiar with the baseline compiler might be able to spot what
> is wrong with the optimization.
>
> Cheers,
> Rafael
Just an FYI, I've been using firefox-21.0.b3,1 f
This is now
http://llvm.org/bugs/show_bug.cgi?id=15882
Someone familiar with the baseline compiler might be able to spot what
is wrong with the optimization.
Cheers,
Rafael
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
OK, I was able to reproduce this. I am trying to reduce the testcase.
On 30 April 2013 14:23, Dimitry Andric wrote:
> On Apr 30, 2013, at 18:34, Jan Beich wrote:
> ...
>> The faulting function is lost within crash handler. If you build
>> firefox with
>>
>> # use DEBUG_FLAGS or set STRIP to emp
On Apr 30, 2013, at 18:34, Jan Beich wrote:
...
> The faulting function is lost within crash handler. If you build
> firefox with
>
> # use DEBUG_FLAGS or set STRIP to empty explicitly
> CFLAGS += ${DEBUG_FLAGS}
> DEBUG_FLAGS += -O0 -g
>
> jaeger jit crash would look like
>
> http://lists.fr
On Apr 30, 2013, at 17:25, Dimitry Andric wrote:
...
> In any case, I have just built the latest Firefox from ports, with clang 3.3,
> and I see no issues at all. At least with approximately 10 minutes of
> browsing, and visiting a varied bunch of sites. I do have it built with
> debug info,
Brandon Gooch writes:
> On Fri, Apr 19, 2013 at 1:06 PM, Florian Smeets wrote:
>> On 19.04.13 19:48, Dimitry Andric wrote:
>>> On Apr 19, 2013, at 17:56, Florian Smeets wrote:
>>>
On 19.04.13 04:01, kit wrote:
> updated current and now firefox and thunderbird both fail to build under
>
On Apr 30, 2013, at 05:28, Brandon Gooch wrote:
...
> Thanks for fixing the build issues.
>
> Now, I've built Firefox with Clang, but the darn thing segfaults at
> the drop of a hat:
>
> $ gdb /usr/local/bin/firefox firefox.core
> ...
> (gdb) bt
> #0 0x0008011eefaa in thr_kill () from /lib/
On Fri, Apr 19, 2013 at 1:06 PM, Florian Smeets wrote:
> On 19.04.13 19:48, Dimitry Andric wrote:
>> On Apr 19, 2013, at 17:56, Florian Smeets wrote:
>>
>>> On 19.04.13 04:01, kit wrote:
updated current and now firefox and thunderbird both fail to build under
the new clang 3.3. has anyo
On 19.04.13 19:48, Dimitry Andric wrote:
> On Apr 19, 2013, at 17:56, Florian Smeets wrote:
>
>> On 19.04.13 04:01, kit wrote:
>>> updated current and now firefox and thunderbird both fail to build under
>>> the new clang 3.3. has anyone seen this or know how to fix?
>>
>> The fix is here:
>>
>>
On Apr 19, 2013, at 17:56, Florian Smeets wrote:
> On 19.04.13 04:01, kit wrote:
>> updated current and now firefox and thunderbird both fail to build under
>> the new clang 3.3. has anyone seen this or know how to fix?
>
> The fix is here:
>
> http://tb.smeets.im/~flo/gecko-clang33-fixes.diff
On 19.04.13 04:01, kit wrote:
> updated current and now firefox and thunderbird both fail to build under
> the new clang 3.3. has anyone seen this or know how to fix?
The fix is here:
http://tb.smeets.im/~flo/gecko-clang33-fixes.diff
It will be committed after the freeze.
Florian
signature.a
updated current and now firefox and thunderbird both fail to build under
the new clang 3.3. has anyone seen this or know how to fix?
gmake[3]: Entering directory
`/tmp/obj/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd10.0/js/src'
/usr/bin/clang++ -o jsanalyze.o -c -I./../
14 matches
Mail list logo