Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Unwinds Gone Wild"
2008 Sep 29
0
[LLVMdev] Unwinds Gone Wild
Whoops, did not send to list:
On Mon, Sep 29, 2008 at 9:01 AM, Duncan Sands <baldrick at free.fr> wrote:
> libgcc is also available for windows.
Really? What license? What restrictions? Any speed impact over the
VC runtimes?
2008 Sep 29
6
[LLVMdev] Unwinds Gone Wild
On Mon, Sep 29, 2008 at 1:50 AM, Duncan Sands <baldrick at free.fr> wrote:
> /* snip */
Just for another voice in here. 'unwind' and its kin would also be
useful for me, especially since this is on platforms without GCC (nor
is GCC used in any way in any step anywhere).
Why does it generate GCC only constructs anyway, that does not sound
very much like the multi-platform that
2008 Sep 30
0
[LLVMdev] Unwinds Gone Wild
Hi,
> On Mon, Sep 29, 2008 at 9:01 AM, Duncan Sands <baldrick at free.fr> wrote:
> > libgcc is also available for windows.
> Really? What license? What restrictions?
search for MinGW and Cygwin. See http://gcc.gnu.org
and http://www.gnu.org for licensing information.
> Any speed impact over the VC runtimes?
I think you are misunderstanding. For certain
operations, eg
2008 Sep 29
0
[LLVMdev] Unwinds Gone Wild
Hi,
> Why does it generate GCC only constructs anyway, that does not sound
> very much like the multi-platform that LLVM is targeting.
since libgcc is available everywhere llvm is, it's as multi-platform
as llvm! If we didn't use libgcc then we'd have to introduce an llvm
runtime library. Since it would just duplicate the functionality of
libgcc, it would introduce an
2008 Sep 29
1
[LLVMdev] Unwinds Gone Wild
Duncan Sands wrote:
>
> since libgcc is available everywhere llvm is, it's as multi-platform
> as llvm! If we didn't use libgcc then we'd have to introduce an llvm
> runtime library. Since it would just duplicate the functionality of
> libgcc, it would introduce an additional maintenance burden without
> bringing any real advantage AFAICS.
>
So if there's
2008 Sep 29
0
[LLVMdev] Unwinds Gone Wild
I guess Duncan's answer in this thread is the best answer to give:
<<Once that [The exception handling stuff needed by llvm-gcc] was done I guess everyone took a breather and kind of forgot about unwind>>
So yes, ultimately, unwind will be supported and clang/llvm should provide its own unwinding runtime.
Patches welcome :)
Cheers,
Nicolas
OvermindDL1 wrote:
> On Mon, Sep
2008 Jul 31
2
[LLVMdev] Unwinds Gone Wild
On Thu, Jul 31, 2008 at 2:19 AM, Duncan Sands <baldrick at free.fr> wrote:
> Hi,
>
> > Can anyone tell me if invoke/unwind is stable in 2.3? I'm seeing some
> > really weird stuff -- unwinds are ending up in seemingly arbitrary
> places...
> > definitely not inside the caller's unwind block My target is x86.
>
> codegen doesn't know how to
2008 Jul 31
0
[LLVMdev] Unwinds Gone Wild
Hi,
> Can anyone tell me if invoke/unwind is stable in 2.3? I'm seeing some
> really weird stuff -- unwinds are ending up in seemingly arbitrary places...
> definitely not inside the caller's unwind block My target is x86.
codegen doesn't know how to handle "unwind" on any target. You need
to call the libgcc unwinding routines directly (or indirectly by
2006 Nov 06
0
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<b>Reid,<br>
<br>
I followed the steps but got stuck as described
2006 Nov 06
4
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
This is an libpath problem. When xgcc runs it wants to dynamically link
the libgcc.so. When you run it from the command line it will find your
system libgcc.so (which works) and so you don't see the segfault. When
you run xgcc from the Makefile, it will have set LD_LIBRARY_PATH to get
your <cfebuilddir>/gcc directory which will find the libgcc.so that it
just built, which is the one
2006 Nov 06
0
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=utf-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Reid,<br>
<br>
Here's the backtrace you asked for:<br>
<br>
2008 Sep 29
2
[LLVMdev] Unwinds Gone Wild
On Mon, 2008-09-29 at 09:50 +0200, Duncan Sands wrote:
> For the moment, yes. If unwind gets implemented one day (I have a plan,
> but no time right now), the implementation is sure to call routines in
> the gcc runtime.
As a transient solution that makes sense, but it seems desirable to have
a generalized unwind scheme that is not tied to libgcc.
shap
2006 Nov 06
2
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
Hi Robert,
On Mon, 2006-11-06 at 12:45 -0800, Robert Mykland wrote:
> Reid,
>
> Here's the backtrace you asked for:
>
> (gdb) bt
> #0 0x0862d65c in llvm::LiveVariables::runOnMachineFunction ()
Hmm, this is a little strange. Your LLVM build is non-debug (there's no
line numbers or arguments in any of the llvm related calls). However,
your llvm-gcc build seems to have
2008 Feb 02
1
CC messed up in RELENG_7 build
The sources were csupped ~3 hours ago. My CC is defined as follows:
env CCACHE_PREFIX=/usr/local/bin/distcc /usr/local/bin/ccache cc
I have done many buildworld, buildkernel and port builds with this setting and
it never caused any problems. However today buildworld fails the following way:
env CCACHE_PREFIX=/usr/local/bin/distcc /usr/local/bin/ccache env CCACHE_PREFIX=/usr/local/bin/distcc
2006 Dec 03
3
[LLVMdev] problem building gcc4 front end on fedora core 5
I'm getting a build error when trying to build gcc4 from sources. This is
for the recent 1.9 release.
How I built llvm-1.9:
-----------------------------
tar zxf llvm-1.9.tar.gz
cd llvm-1.9/
./configure --prefix=/custom/llvm-1.9
make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION='-O2' tools-only
make install
How I built gcc4:
-----------------------------
export
2008 Sep 27
4
[LLVMdev] Unwinds Gone Wild
Duncan Sands wrote:
>> I can't find any information about cxa_throw at all, not even a type
>> signature. If I could, could I just call it as if it were unwind, and it
>> would be caught by invoke?
>>
>
> cxa_throw comes from the gcc C++ runtime. In order to see how to throw
> and catch things correctly using it, compile some C++ examples down to
>
2007 Feb 28
1
[LLVMdev] Cygwin release build error
I did not realize that '--enable-llvm' was required and that invalidates my debug build results which were built just with LLVM on the path.
I am now getting a segmentation fault when doing a 'make install' on LLVM-GCC4, possibly validating my original thoughts that GCC 4.1.1 was required to build LLVM-GCC 4.0.1. I will try using GCC 4.1.1.
Heres the error anyway :-
make[2]:
2007 Mar 01
3
[LLVMdev] compiling llvm-gcc4 on ubuntu
hello,
i am new to llvm and can't manage to compile the gcc backend.
my steps:
i compile the llvm-source first as suggested in "README.LLVM"
that works fine and without any issues.
then i make a new dir called build. from there i do the following:
stefan at ubuntu:~/programs/llvm/build$ ../llvm-gcc4-1.9.source/configure --enable-languages=c,c++ --prefix=/usr/local/
2008 Jul 31
4
[LLVMdev] Unwinds Gone Wild
Can anyone tell me if invoke/unwind is stable in 2.3? I'm seeing some
really weird stuff -- unwinds are ending up in seemingly arbitrary places...
definitely not inside the caller's unwind block My target is x86.
As a simple test, I tried to compile the following code and I got a
segmentation fault. It looks good to me. Can someone help me out or is
this a bug?
define i32 @foo() {
2007 Jan 10
4
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
The machine is a Dell workstation with xeon processors. The OS is RHEL 4 AS
x86_64
gcc version is 3.4.6
I checked out the llvm-gcc from svn, configured with
../llvm-gcc/configure --prefix=$HOME/llvm-gcc-install
--enable-llvm=$HOME/llvmobj/ --enable-languages=c,c++ --enable-checking
--disable-shared --disable-multilib
and get the following error message:
make