search for: __mulhi3

Displaying 9 results from an estimated 9 matches for "__mulhi3".

Did you mean: __muldi3
2019 Jun 11
3
How to tell LLVM to treat Commutable library calls as such, for example multiplication?
...generated by Clang thus missing possible optimisations. For example, the following IR code ; Function Attrs: minsize norecurse nounwind optsize readnone define dso_local i16 @multTest(i16 %a, i16 %b) local_unnamed_addr #0 { entry: %mul = mul i16 %b, %a ret i16 %mul } is lowered as it is to a __mulhi3 library call with the arguments reversed as shown (b,a). This is suboptimal because later on this requires an intermediate register to swap them. SelectionDAG has 9 nodes: t0: ch = EntryToken t4: i16,ch = CopyFromReg t0, Register:i16 %1 t2: i16,ch = CopyFromReg t0, Register:i16 %0...
2006 Nov 06
0
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
...-source/gcc/libgcc2.c:43:16: error: tm.h: No such file or directory<br> In file included from ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:64:<br> ../../llvm-gcc4-1.8-source/gcc/libgcc2.h:214:3: error: #error "expand the table"../../llvm-gcc4-1.8-source/gcc/libgcc2.c: In function ‘__mulhi3’:<br> ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: ‘BITS_PER_UNIT’ undeclared (first use in this function)<br> ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: (Each undeclared identifier is reported only once<br> ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: fo...
2006 Apr 22
3
[LLVMdev] Building CFE on MinGW
...tory ./tm.h:11:23: defaults.h: No such file or directory In file included from ../../src/gcc/libgcc2.c:44: ../../src/gcc/llvm-out.h:69: error: syntax error before '*' token ../../src/gcc/llvm-out.h:69: warning: function declaration isn't a prototype ../../src/gcc/libgcc2.c: In function `__mulhi3': ../../src/gcc/libgcc2.c:502: error: `BITS_PER_UNIT' undeclared (first use in this function) ../../src/gcc/libgcc2.c:502: error: (Each undeclared identifier is reported only once ../../src/gcc/libgcc2.c:502: error: for each function it appears in.)
2006 Nov 06
1
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
Hi Robert, Please make sure that you: 1. Completely rebuild LLVM (make clean; make reconfigure; make tools-only) 2. Completely rebuild llvm-gcc (wipe out the build dir with rm -rf, configure llvm-gcc and rebuild it) If you've done that, then please enter the debugger and get a stack trace for us. You will need to: 1. Capture the xgcc compile command that failed 2. Run that command
2006 Nov 06
4
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
...ce/gcc/libgcc2.c:43:16: error: tm.h: No such > file or directory > In file included from ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:64: > ../../llvm-gcc4-1.8-source/gcc/libgcc2.h:214:3: error: #error "expand > the table"../../llvm-gcc4-1.8-source/gcc/libgcc2.c: In function > ‘__mulhi3’: > ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: ‘BITS_PER_UNIT’ > undeclared (first use in this function) > ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: (Each undeclared > identifier is reported only once > ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: for eac...
2017 Oct 05
3
Bug 20871 -- is there a fix or work around?
Looks like I have run into the same issue reported in: https://bugs.llvm.org/show_bug.cgi?id=20871 Is there a fix or work-around for it? The bug report seems to be still open. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171005/46c1282d/attachment.html>
2006 Nov 06
0
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
...../../llvm-gcc4-1.8-source/gcc/libgcc2.c:43:16: error: tm.h: No such file or directory In file included from ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:64: ../../llvm-gcc4-1.8-source/gcc/libgcc2.h:214:3: error: #error "expand the table"../../llvm-gcc4-1.8-source/gcc/libgcc2.c: In function ‘__mulhi3’: ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: ‘BITS_PER_UNIT’ undeclared (first use in this function) ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: (Each undeclared identifier is reported only once ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: for each function it appears in....
2006 Nov 06
3
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
I was having video problems, so upgraded my Linux box from SUSE 9.3, where LLVM frontend 4 source built fine, to SUSE 10.1, where I got the error message: ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:541: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://llvm.org/bugs> for instructions. This version of SUSE
2006 Nov 06
2
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
...> > file or directory > > > In file included from ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:64: > > > ../../llvm-gcc4-1.8-source/gcc/libgcc2.h:214:3: error: #error "expand > > > the table"../../llvm-gcc4-1.8-source/gcc/libgcc2.c: In function > > > ‘__mulhi3’: > > > ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: ‘BITS_PER_UNIT’ > > > undeclared (first use in this function) > > > ../../llvm-gcc4-1.8-source/gcc/libgcc2.c:535: error: (Each undeclared > > > identifier is reported only once > > > ../../llvm...