Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] bugpoint question"
2008 May 29
0
[LLVMdev] bugpoint question
I believe I can use bugpoint to help you folks track down an LLVM bug
using the bugpoint mode where it runs the program and looks at its output.
However there is a slight complication: to distinguish between correct
and incorrect runs I need to run the program under test in our hacked
valgrind. After reading all the bugpoint docs I can't figure out how I
would do that. What I would like
2013 Mar 27
8
[LLVMdev] [cfe-dev] Handling SRet on Windows x86
Hi Eric,
> From my perspective Win32 is the windows ABI and mingw and cygwin are their own ABIs
No. They are using Windows Platform ABI for almost everything (e.g.
calling API, C runtime, etc.). At least mingw does. The differences
are exactly in unspecified area (e.g. passing / returning structs by
value).
The only difference is C++, where mingw / cygwin follows Itanium ABI
and MSVC - its
2007 Aug 29
1
[LLVMdev] RFC: Patch for Exceptions
Hello, Bill
> It may be my lack of understanding, but it appears that having --
> enable-eh set during compilation of llvm-gcc is causing extra files
> to be compiled.
Oh, no. They are always compiled.
> They do. However, it doesn't seem to stop it from failing during
> compilation of unwind-dw2.c for libgcc -- it has
> "__builtin_eh_return" in it. During
2009 Nov 18
0
[LLVMdev] Information generated by Bugpoint
Hello
> What does this information mean?
As written in the assertion - C backend does not support arbitrary
bitwidth integers.
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
2009 Jul 11
0
[LLVMdev] Heads up! Working on bugpoint
Hello, David
> bugpoint now works for remote ARM if you run it directly from the
> command line. It doesn't work correctly when invoked from the test
> makefile because envvar PWD is being set to /bin/pwd and so causing
> GCC::ExecuteProgram to do the wrong thing. I'm not sure what is going
> on with that, perhaps something in the makefile hierarchy is setting
> PWD to
2007 Feb 28
0
[LLVMdev] Cygwin release build error
Hello, Aaron.
> /usr/src/llvm-gcc4/gcc/libgcc2.c: In function '__eprintf':
> /usr/src/llvm-gcc4/gcc/libgcc2.c:1832: internal compiler error:
> Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://llvm.org/bugs> for instructions.
You should:
1. Try to emit bytecode with --emit-llvm compiler switch.
1.1
2007 Sep 28
5
[LLVMdev] Vector troubles
Chuck,
> It is dying trying to store a our working vector into one of the LLVM
> vectors created on the stack. Despite the align-16 directive on the
> alloca instruction, it is not always aligning to a 16-byte boundary.
The stack is not necessary 16 bytes aligned on linux/windows. The vector
is really sotred aligned relative to %esp, but %esp value is not good.
This is known problem
2009 Nov 18
4
[LLVMdev] Information generated by Bugpoint
Hi,all
I ran my generated whole-program bitcode file which performs as a bodytrack
tool, it can give me the right result but with a stack dump before it exsits
Update Error : Model observation failed for time : 1
Error loading observation data
terminate called after throwing an instance of 'std::bad_cast'
what(): std::bad_cast
0 lli 0x08b713d2
1 lli 0x08b71247
2007 Aug 29
0
[LLVMdev] RFC: Patch for Exceptions
On 8/29/07, Anton Korobeynikov <asl at math.spbu.ru> wrote:
> Hello, Bill
>
> > It may be my lack of understanding, but it appears that having --
> > enable-eh set during compilation of llvm-gcc is causing extra files
> > to be compiled.
> Oh, no. They are always compiled.
>
> > They do. However, it doesn't seem to stop it from failing during
> >
2007 Sep 30
1
[LLVMdev] Vector troubles
Hello, Daniel.
> glibc < 2.4 don't reliably keep stack at 16 bytes through some calls
> (qsort, etc), but otherwise, it stays 16 byte aligned.
Interesting, but why in this case stuff like 'force_align_arg_pointer'
required?
--
With best regards, Anton Korobeynikov.
Faculty of Mathematics & Mechanics, Saint Petersburg State University.
2012 Oct 04
3
[LLVMdev] [cfe-dev] Handling SRet on Windows x86
> Ah, got it.
> Sounds like we might need to introduce CC_X86_Win32_MSVC_ThisCall then?..
No, we should not. It should be properly expanded in frontend.
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
2013 Mar 28
0
[LLVMdev] [cfe-dev] Handling SRet on Windows x86
> How can having an MSVC compatible compiler be to the detriment of clang and
> llvm? No one is trying to break mingw here, merely add support for something
Just to make stuff clear: I just wanted proper naming which will be
non-confusing. Right now we have:
- isTargetWindows() which really means "msvc-compabile"
- isTargetWin32() which means "everything on windows", so
2006 May 24
3
[LLVMdev] Error with llc after using llvm-g++ WIN32
Hello, Ashwin.
You wrote Wednesday, May 24, 2006, 11:25:11 AM:
AC> "Pass::getClassPassInfo<PassClass>() "Pass class not
AC> registered!"" failed: file
AC> "/cygdrive/c/llvm/llvm/include/llvm/PassAnalysisSupport.h", line 76
AC> Aborted
Same for me.
AC> Wihtout the -march specified (using native x86 assembly) it does
AC> convert it into
2008 Sep 21
2
[LLVMdev] OpenBSD port in progress
Hello,
> If anybody has an idea of how to fix this (other than using another
> version of gcc because I am sick of compiling), I would appreciate. I
> can offer backtraces or shell access if anybody is interested, just
> ask me what you need.
This was fixed couple of months ago. Please consider using current svn
top of tree, not 2.3 release.
--
WBR, Anton Korobeynikov
2008 Jul 16
2
[LLVMdev] bugpoint / cbe Problems
Hello, David.
> After hacking around in the CBE output I managed to compile it with
> gcc, only to discover that gcc 4.1.2 has the SAME bug LLVM does with
> respect to alignment.
Automatic stack realignment was atted to X86 backend ~3 months ago. Everything should
work with LLVM. If not - please fill out a PR. AFAIR, automatic stack realignment still does
not land into gcc mainline
2007 Jun 24
5
[LLVMdev] alloca on Win32
Hello, Scott.
> Checking the assembly from llc, the first alloca call is to allocate
> local vars in _main. Is this just the state of the code at 2.0 when
> built with vs.net, or is there something that I've managed to
> mis-build locally?
_alloca is used to probe the stack, if you asks for locals of size more
that 4k. This is pretty ugly, but the names of this functions differs
2012 Oct 04
0
[LLVMdev] [cfe-dev] Handling SRet on Windows x86
How can a frontend tell LLVM to put a function argument on stack/register/etc?
On Thu, Oct 4, 2012 at 5:08 PM, Anton Korobeynikov <asl at math.spbu.ru> wrote:
>> Ah, got it.
>> Sounds like we might need to introduce CC_X86_Win32_MSVC_ThisCall then?..
> No, we should not. It should be properly expanded in frontend.
>
> --
> With best regards, Anton Korobeynikov
>
2008 Sep 21
0
[LLVMdev] OpenBSD port in progress
2008/9/21 Anton Korobeynikov <asl at math.spbu.ru>:
> Hello,
>
>> If anybody has an idea of how to fix this (other than using another
>> version of gcc because I am sick of compiling), I would appreciate. I
>> can offer backtraces or shell access if anybody is interested, just
>> ask me what you need.
> This was fixed couple of months ago. Please consider
2007 Oct 01
1
[LLVMdev] Vector troubles
I tried to ask for 32 and that didn't seem to help. MallocInst also
seemed to ignore the 16 byte directive. For now, I'm just issuing all
my loads as unaligned and that's working ok.
Thanks,
Chuck.
-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
On Behalf Of Evan Cheng
Sent: Monday, October 01, 2007 10:35 AM
To: asl at
2007 May 04
2
[LLVMdev] LLVM-GCC Source Updated?
Hello, Bill.
> Has anyone gotten the latest/greatest sources from the LLVM-GCC open
> source server lately?
No. It's still at rev 319 (as of 29.04).
--
With best regards, Anton Korobeynikov.
Faculty of Mathematics & Mechanics, Saint Petersburg State University.