Displaying 20 results from an estimated 2000 matches similar to: "Cross Compilation Problem"
2018 Sep 05
2
AddressSanitizer on SPECCPU2006
Hi Alex
Thanks for your email. But it seems not work. I removed the
-fsanitize=address flag.
The global buffer overflow message doesn't show. However, no *.sancov file
is created after I run perlbench. Thus, I could not get the BB coverage. Do
you have any ideas? Many Thanks
Regards
Muhui
Alexander Potapenko <glider at google.com> 于2018年9月5日周三 下午7:14写道:
> Hi Muhui,
>
> If
2018 Sep 05
2
AddressSanitizer on SPECCPU2006
Hi
If so, is it able to disable this check. All I need is just to get the BB
coverage information
Regards
Muhui
Alexander Potapenko <glider at google.com>于2018年9月5日 周三下午6:57写道:
> This is a known problem in SPECCPU2006, see
> https://github.com/google/sanitizers/wiki/AddressSanitizerFoundBugs
> On Wed, Sep 5, 2018 at 7:36 AM Muhui Jiang via llvm-dev
> <llvm-dev at
2018 Sep 05
2
AddressSanitizer on SPECCPU2006
Hi
I am using SanitizerCoverage feature supported by clang to get the
basicblock coverage.
my tested binaries are spec cpu2006. I compiled the binary with the option
COPTIMIZE = -O0 -fsanitize=address -fsanitize-coverage=bb -flto
-fno-strict-aliasing -std=gnu89 -gdwarf-3
After the compiling process is end. I run the 400.perlbench. with the
command
ASAN_OPTIONS=coverage=1 ./perlbench.
2020 Sep 14
2
Cross compiling for ARMv7-m
Hi Peter,
On Wed, 26 Feb 2020 at 18:37, Peter Smith via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> Hello Arslan,
>
> > I am guessing I can borrow libraries such as lc and lm from GCC
> > arm-none-eabi*, but for clang_rt.builtins-arm.a (which I thought
> > should've been built with LLVM build but I couldn't find that library
> > in my build
2018 Nov 08
2
Compile with both arm and thumb mode
Hi
I would like to use clang to cross compile the ARM binary. I hope the
target binary contains both arm and thumb instruction sets.
I use the flag -mhwdiv=arm,thumb. I compiled several binaries. However, I
found that the thumb mode instructions are few. Even for very big program
like gcc. The number of thumb mode instruction is less than 100. I get the
ground truth from the mapping table.
2020 Feb 26
2
Cross compiling for ARMv7-m
Hi,
I am trying to use LLVM/clang to build a binary for ARM Cortex M platforms.
When I build my binary the linker fails to find these libraries.
./bin/clang++ -target arm-none-eabi -mcpu=cortex-m4 ./temp.cpp -L
./lib/ -L ./libexec/ -L ../build3_v7m/lib/
ld.lld: error: unable to find library -lunwind
ld.lld: error: unable to find library -lc
ld.lld: error: unable to find library -lm
ld.lld: error:
2015 Jun 11
4
idmap & migration to rfc2307
Yup, strange - right!
Samba 4.2.2
RFC2307 attributes were added as follows:
# sed -e 's/${DOMAINDN}/dc=MYDOMAIN,dc=MY,dc=TLD/g' \
-e 's/${NETBIOSNAME}/MYDOMAIN/g' \
-e 's/${NISDOMAIN}/MYDOMAIN/g' \
/usr/local/samba/share/setup/ypServ30.ldif > ypServ30-JMH.ldif
# service samba4 stop
# ldbmodify -H
2015 Jun 05
3
Added RFC2307 --> Unable to convert SID (S-1-1-0)
>From my .bash_history on the schema master DC, effectively:
# sed -e 's/${DOMAINDN}/dc=MYDOMAIN,dc=MY,dc=TLD/g' \
-e 's/${NETBIOSNAME}/MYDOMAIN/g' \
-e 's/${NISDOMAIN}/MYDOMAIN/g' \
/usr/local/samba/share/setup/ypServ30.ldif > ypServ30-JMH.ldif
# service samba4 stop
# ldbmodify -H /usr/local/samba/private/sam.ldb
2018 Nov 03
2
llvm bug 36466 fix
Hi Dave
I am not going to access any hardware. I am using clang to analysis the ARM
binaries. The binary is 483.xalancbmk in CPU SPEC2006. When I use the
optimization O0, no crash will occur. The crash occurs when I set
optimization level as O1,O2,O3 and Os.
If I have to recompile and rerun the tests. What version of llvm is
suggested. It would be better if anyone could provide the patch on this
2018 Nov 03
2
llvm bug 36466 fix
Hi Dave
Sorry, I meant the hardware you're using to compile LLVM - you mentioned it
took you a long time to rebuild it so it would be hard for you to
write/experiment on tests.
=============================
Compiling LLVM doesn't take me too much time(less than 2 hours). The
hardware is good enough and I am using interl E5 CPU. What I mean is that
it took me a long time to analysis the
2018 Nov 03
2
llvm bug 36466 fix
Hi
I come across the following exception when I use the llvm-dwarfdump
-debug-info target_binary:
llvm-dwarfdump: /home/linux/llvm-7/llvm/lib/MC/MCRegisterInfo.cpp:87: int
llvm::MCRegisterInfo::getLLVMRegNum(unsigned int, bool) const: Assertion `I
!= M+Size && I->FromReg == RegNum && "Invalid RegNum"' failed.
Stack dump:
0. Program arguments:
2018 Jul 23
2
Requesting for help.
Hello All,
I need some help with respect to cross compiling for ARM.
While trying to cross compile for the ARM target, I am hitting some errors.
I need some help in this.
I use the following command to cross compile for ARM Cortex A72 (ARM v8-a),
64 bit architecture:
*cmake -v CC='clang' CXX='clang++'
-DCMAKE_C_COMPILER=../build_directory_llvm/bin/clang
2018 Sep 03
4
Basic Coverage
Hi
My goal is that given a binary and the corresponding input. I want to know
what IR level basic blocks are covered. I need the detail information,
which is the set of all the covered BBs rather than just a number.
I want to know whether there are some tools that can support this
requirements. If not, I think maybe instrumentation can helps. However, I
do not know too much about this. Any
2018 Jun 26
2
Instruction boundaries
There should be a line-table entry for the end of the function, which appears to be missing from the dump you provided. llvm-dwarfdump should report this address with 'end_sequence' in the Flags. Are you using a different dumper?
I am not sure but my guess would be that inline data is not represented in the line table. The line table's primary purpose is to inform the debugger
2018 Jun 26
2
Instruction boundaries
Hi paulr
Thanks for your reply. Though DWARF info give me the code address ranges,
there might be inline data. If so, how to handle this case?
As for the dwarf line table. Sometimes, the source line might be zero. Do
you know why? If all instructions should be describe in the line table, I
think analyzing Dwarf line table is enough to get all the instructions
addresses. Do you agree?
I would
2018 Jun 26
2
Instruction boundaries
I'm not familiar with the target instruction set, but if "MOV PC, R0" is not a return instruction, I'm guessing that the sequence starting at A39C is a dispatch through a jump table. The jump table would be considered part of the instruction stream and included in the scope of the line table. This is not a case where you would see end_sequence; my mistake.
The line table does
2018 Jun 12
4
IR to binary address mapping
Hi
I know that LLVM provide some debug API for us to know the source code
information. For example, every IR instruction's source line number and
column number.
However, are there any method to get a mapping from IR instruction to
binary address directly. I don't want to use dwarf line mapping table as a
bridge. I think the binary is generated by clang and llvm. I think there
definitely
2018 Jun 13
2
IR to binary address mapping
Hi Paul
Thanks for your comments. Suppose I can generate the control flow graph via
LLVM Pass or the default option like '-dot-cfg' with opt. However, the
control flow graph is based on llvm IR level. I would like to have a
control flow graph based on binary level. Thus, I want to map the IR to
binary address.
As far as I know, we used to use the debug information to map the IR to
source
2018 Jun 13
2
IR to binary address mapping
Hi
However, frontend may also do various operations on the source code and one
line number and column number could map to more than one binary address.
Why LLVM IR cannot?
Regrads
Muhui
2018-06-12 23:18 GMT+08:00 mayuyu.io <admin at mayuyu.io>:
> In theory that’s not exactly possible/accurate. Due to various operations
> in the Backend like Instruction Legalization, one IR
2017 Oct 07
2
Bug 20871 -- is there a fix or work around?
Ignore the suggested fix in my earlier post. How about this?
diff --git a/lib/Target/X86/X86ISelLowering.cpp b/lib/Target/X86/X86ISelLowering.cpp
index 20c81c3..b8ebf42 100644
--- a/lib/Target/X86/X86ISelLowering.cpp
+++ b/lib/Target/X86/X86ISelLowering.cpp
@@ -1632,10 +1632,11 @@ X86TargetLowering::X86TargetLowering(const X86TargetMachine &TM,
if (!Subtarget.is64Bit()) {
// These