similar to: [LLVMdev] Fwd: [cfe-dev] freebsd-mips64 unhandled .cpsetup

Displaying 20 results from an estimated 100 matches similar to: "[LLVMdev] Fwd: [cfe-dev] freebsd-mips64 unhandled .cpsetup"

2015 Feb 16
2
[LLVMdev] [cfe-dev] freebsd-mips64 unhandled .cpsetup
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 02/09/15 09:09, Toma Tabacu wrote: > >> Toma: >> >> Hey, I'm the bsd nerd trying to get our mips target switched over >> to clang/llvm. I looked at switching the mips asm parser over >> to parseExpression() but I am unfamiliar with the syntax to do >> this for .cpsetup. >> >> If you do
2015 Dec 08
3
compiler-rt fails to find <stdarg.h> on FreeBSD
I'm unsure why this is failing this week, but when I build for FreeBSD HEAD, I now get a failure to find <stdarg.h>. Very strange. Maybe its missing a -I /usr/include somewhere? [1950/2811] Building CXX object projects/compiler-rt/lib/tsan/CMakeFiles/clang_rt.tsan-x86_64.dir/rtl/tsan_interceptors.cc.o FAILED: /usr/bin/CC -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
2013 Nov 09
1
10.0 BETA 3 with redports kernel panic
The redbuild boxes for redports are doing a very good and reliable job getting kernel panics out of 10.0: http://people.freebsd.org/~sbruno/redbuild_panic.txt Pretty frequent and pretty nasty. Happening on multiple machines under load. sean -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc:
2012 Apr 16
2
ATI Radeon 4250 in Dual Head Config?
My xorg.conf foo is pretty weak today. Does anyone have an ATI 4250 in a dual head config? I'd be interested in looking over your xorg.conf. Sean p.s. Mine at the moment, that doesn't work very well: http://people.freebsd.org/~sbruno/4250_xorg_conf.txt
2010 Feb 17
2
[LLVMdev] Kaleidoscope toy4 failure seg fault on llvm::ExecutionEngine::getTargetData (this=0x0)
I am new to llvm so I might be missing a critical step. My system is Fedora 12 but this also happens in Mac OS X 10.6.2. Here are the steps I used to compile llvm: export TARGETS=x86,x86_64,cpp export INSTALLDIR=/home/rovitotv/llvm ../llvm-2.6/configure --prefix=$INSTALLDIR --enable-bindings=none --enable-targets=$TARGETS --enable-optimized --with-llvmgccdir=$INSTALLDIR
2009 Oct 01
3
[LLVMdev] PHI and Allocas
Hi, I'm incrementing my toy compiler to account for variable mutations around if/else blocks. Reading the Kaleidoscope tutorial, I've learnt that I can substitute the PHI node creation by allocas and retrieving the value later, if needed. The Kaleidoscope example seems to account for one value only, the result of: Value *ThenV = Then->Codegen(); (...) Value *ElseV =
2010 Jun 21
2
[LLVMdev] MC: Object file specific parsing
Hi Daniel, attached is a patch that pushes most of the object file specific parsing out of AsmParser and down into MachOAsmParser. This was done as a cleanup for the ELF work. I know that you're not happy with this approach, particularly the fact that as we add more object file formats and assembler dialects, it's going to cause a class explosion. But I was hoping that we could use this
2012 May 27
2
[stable 9]Dell R620 Ethernet Ordering
I'm trying to understand the newbus and acpi interactions on this Dell R620 that result in the Broadcom adapter board being probed "backwards" or just plain out of order in comparison to the connector layout and the linux tg3 driver. We seem to be detecting PCI0:2:0 before PCI0:1:0. This seems odd to me. When I replace the broadcom daughter card with an intel daughter card, this
2010 Feb 17
0
[LLVMdev] Kaleidoscope toy4 failure seg fault on llvm::ExecutionEngine::getTargetData (this=0x0)
First, you have to call llvm-g++ to use the llvm-gcc front end, but it doesn't matter here. I'd like to suggest that you use pastebin to put your code and the send us the link, so that we can download it. The problem is that TheExecutionEngine is set to NULL (maybe because of a previous error), but it will be really better if you use pastebin. On Wed, Feb 17, 2010 at 6:01 AM, Todd Rovito
2012 Jul 13
2
stable/9 panic Bad tailq NEXT(0xffffffff80e52660->tqh_last) != NULL
Well this is new. I haven't a clue what Dell has done on this R620, but this popped up today after I did a boat load of BIOS updates and tried to install stable/9 from our yahoo tree. If anyone sees the obvious solution here, I'd love to figure it out. found-> vendor=0x14e4, dev=0x165f, revid=0x00 domain=0, bus=2, slot=0, func=1 class=02-00-00, hdrtype=0x00, mfdev=1
2011 Feb 08
1
[LLVMdev] Question about linker error
Hello all, When extending the tutorial to support global variables I'm getting the following linker error: glob.o:glob.cpp:(.text+0x12241): undefined reference to `vtable for GlobalExprAST' collect2: ld returned 1 exit status GlobalExprAST class is: /// GlobalExprAST - Expression class for globals class GlobalExprAST : public ExprAST { std::string Name; ExprAST *Init; public:
2013 Dec 21
3
[LLVMdev] running clang format on the Mips target
Hi David, What kind of "a lot of out-of-tree changes"? You should push changes incrementally as you do work. Holding onto changes means that many things, not just reformatting, can make them need to be redone. We frequently clean up and rewrite code to make it cleaner and easier to maintain. We are moving to a more strict internal review and pushing of changes and post commit
2015 May 15
3
[LLVMdev] MIPS asm backend emitting weird symbols into object file?
I'm cross-compiling for MIPS. The test-case is as simple as it can be: void foo() {} $clang -target mips64-octeon-linux -c -B path/to/cross/compiled/mips/assembler a.c And then I look at the object file: $ nm a.o 0000000000000020 t $tmp0 0000000000000000 T foo I would like to know what "$tmp0" is. Furthermore, if I pass -g to clang, I see a whole bunch of such symbols. Some of
2010 Feb 17
1
[LLVMdev] Kaleidoscope toy4 failure seg fault on llvm::ExecutionEngine::getTargetData (this=0x0)
On Wed, Feb 17, 2010 at 6:29 AM, Conrado Miranda <miranda.conrado at gmail.com> wrote: > First, you have to call llvm-g++ to use the llvm-gcc front end, but it > doesn't matter here. I got the compile command from the Kaleidoscope documentation. > I'd like to suggest that you use pastebin to put your code and the send us > the link, so that we can download it. The
2013 Dec 19
1
[LLVMdev] [PATCH] MC: handle .cfi_startproc simple
Really sorry I missed this. Just found it looking for something else in my inbox. I think we should support this but * We should still err on other identifiers ".cfi_startport bar" is invalid. * If I read the gas documentation correctly, the effect of "simple" is to skip the initial cfi instructions. We should test if that is the case and implement it too. Accepting and
2013 Dec 24
2
[LLVMdev] running clang format on the Mips target
Hi David, I agree with you that it would be rude to simply clang-format the MIPS backend without coordination with any out-of-tree derivatives. To be honest, it hadn't occurred to me that there would be any such derivatives and the possibility wasn't raised in our internal discussion before we brought the subject up on this list. I'm keen to coordinate with such derivatives to
2009 Oct 01
0
[LLVMdev] PHI and Allocas
On Thu, Oct 1, 2009 at 4:35 PM, Renato Golin <rengolin at systemcall.org> wrote: > Hi, > > I'm incrementing my toy compiler to account for variable mutations > around if/else blocks. > > Reading the Kaleidoscope tutorial, I've learnt that I can substitute > the PHI node creation by allocas and retrieving the value later, if > needed. The Kaleidoscope example
2008 Feb 22
1
[LLVMdev] tutorial typos
There were some typos in the tutorial. This patch should fix them: index b7f968b..50619e0 100644 --- a/docs/tutorial/LangImpl2.html +++ b/docs/tutorial/LangImpl2.html @@ -933,7 +933,7 @@ public: /// of arguments the function takes). class PrototypeAST { std::string Name; - std::vector&lt; Args; + std::vector&lt;std::string&gt; Args; public: PrototypeAST(const std::string
2015 Mar 06
0
[klibc:master] add-mips64-support-arch-mips64-specific
Commit-ID: 3438d861da2e6939a6b0d454ffe247c19ead5993 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=3438d861da2e6939a6b0d454ffe247c19ead5993 Author: Dejan Latinovic <Dejan.Latinovic at imgtec.com> AuthorDate: Thu, 5 Mar 2015 16:51:45 -0800 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Thu, 5 Mar 2015 16:51:45 -0800
2009 Dec 10
0
samba-3.3 cross compiling error on mips64-octeon-linux
Hi I need to build samba-3.3.3 on a board with mips processor. so I executed configures with theses options ../configure --target=mips64-octeon-linux-gnu --host=mips64-octeon-linux-gnu --prefix=/usr/local/etc/smb ? Search from?config.log error on line 76308. Why it care host header files (see red line), instead of the cross header?files? ? configure:76308: mips64-octeon-linux-gnu-gcc -c - -O -O