search for: xcllnt

We have upgraded a box from 6.2 to 6.3-RELEASE. Afterwards the box does not recognize its ST Lab I-160 serial card with Netmos 9845 Chipset. It worked flawlessly on 6.2 with puc(4) driver. >From dmesg: pci1: <simple comms, UART> at device 8.0 (no driver attached) ~# pciconf -l -v | grep -B 4 UART none2@pci1:8:0: class=0x070002 card=0x00041000 chip=0x98459710 rev=0x01 hdr=0x00

...e correct fix is to enhance llvm::TargetLowering::getRegForInlineAsmConstraint(), can someone give me some pointers as to how to fix it? I have no experience with the code and like to get my hands dirty... Thanks, BTW: Is there a cross-reference of the project somewhere? -- Marcel Moolenaar xcllnt at mac.com

...ations = > {<llvm::SmallVectorImpl<<unnamed>::InequalityGraph::Edge>> = {Begin = > 0x5a5a5a5a, End = 0x5a5a5a5a, Capacity = 0x5a5a5a5a, FirstEl = 90 > 'Z'}, InlineElts = 'Z' <repeats 47 times>}} > > FYI, > > -- > Marcel Moolenaar > xcllnt at mac.com > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

...*N $2 = {_vptr$Node = 0x5a5a5a5a, Relations = {<llvm::SmallVectorImpl<<unnamed>::InequalityGraph::Edge>> = {Begin = 0x5a5a5a5a, End = 0x5a5a5a5a, Capacity = 0x5a5a5a5a, FirstEl = 90 'Z'}, InlineElts = 'Z' <repeats 47 times>}} FYI, -- Marcel Moolenaar xcllnt at mac.com

...ace to do the right thing. I don't know yet why it didn't though. Ideally the problem should be handled by the abstract datatype itself. An indirect iterator, either the addition of one or replacing the current unsafe iterator with one, should be a good solution. FYI, -- Marcel Moolenaar xcllnt at mac.com

...hich seems to need authentication, so may not be open for business just yet. I'll finish up configuration and I'll be setting up some more infrastructure (buildbot, etc) in due time, but for now: It's a baby girl project! Father is doing fine... :-) Cheers, -- Marcel Moolenaar xcllnt at mac.com

...ters from the class. 3820 RegClassRegs = TLI.getRegClassForInlineAsmConstraint(OpInfo.ConstraintCode, 3821 OpInfo.ConstraintVT); Is it me or is the comment not really applicable to this particular case? thanks, -- Marcel Moolenaar xcllnt at mac.com

On Tue, 20 May 2008, Marcel Moolenaar wrote: > On May 20, 2008, at 1:45 PM, Marcel Moolenaar wrote: >> The following IR is causing the assert: The issue here is that the IA64 backend doesn't have inline asm support yet. This should be pretty easy to add. Take a look at the X86 version: X86TargetLowering::getRegForInlineAsmConstraint it just maps "r" onto the GPR

...related define that could also be used to select the right inline assembly statement is: #define __GNUCLIKE_ASM 3 In any case, register naming in inline assembly on FreeBSD is the same as the Linux version, so maybe the condition can be simplified and based on the OS? FYI, -- Marcel Moolenaar xcllnt at mac.com

Hello, Marcel First of all, thank for your great job for trying llvm-gcc on FreeBSD! Some quick notes below: > o Adding support for inline assembly for ia64 (already started) and > improving ia64 in general. This is longer term work... Please note, that IA64 didn't have active maintainer for some time (maybe year or even two), so it can be heavily broken for some things. I bet

Hi, I am running FreeBSD 5.0-RELEASE-p7 and cannot build any Mozilla version from ports. The build exits for all versions at the same point. A source file called jsdtoa.c. Thanks.. Here is my error report: ******************************************************************************* cc -o jsdtoa.o -c -DOSTYPE=\"FreeBSD5\" -DOSARCH=\"FreeBSD\" -DEXPORT_JS_API

...tree for a bit longer, but disconnect it? BTW: I don't run Linux at all, so no Linux/ia64 support. I can see how that could be a problem for people. Anyway: my case is a weak one and I would understand if the target get axed without considering my email/request... FYI, -- Marcel Moolenaar xcllnt at mac.com

Hello, LLVM's IA-64 target has not been maintained for a few years, and it is currently unable to compile many simple testcases. I'm planning to remove it from the tree soon, unless someone objects. Dan

Hi, I had a power failure, and the on-disk configuration for vinum went bizarre. The logs read from disks are at http://biaix.org/pk/debug/ (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead drive? Can I force vinum to use the other's drive configuration? What's the less traumatic

Thanks for tracking this down! I can't seem to reproduce it on Linux, even with valgrind. Can you try out this patch and let me know whether it works? Nick Marcel Moolenaar wrote: > On May 26, 2008, at 1:25 AM, Bill Wendling wrote: > >> On May 25, 2008, at 1:39 PM, Marcel Moolenaar wrote: >>> On May 25, 2008, at 12:58 AM, Bill Wendling wrote: >>>

...or do you prefer something less public (protecting the LLVM "brand" comes to mind)? I'll watch the commit logs and when I see ia64 being axed, I'll pick the latest release (2.5 right now, but maybe 2.6) and use that as the basis for the work. Cheers, -- Marcel Moolenaar xcllnt at mac.com

Chris Lattner wrote: > On Mon, 16 Jun 2008, Gary Benson wrote: > > When you genetate code on PowerPC you need to explicitly > > invalidate the instruction cache to force the processor to reread > > it. In LLVM there is code to do this for function stubs on > > Macintosh, but not for other platforms and not for JITted code > > generally. > > Applied, thanks!

...has a vested interest in LLVM. HP and Intel have their own compilers and if they work on some open source compiler, it's either GCC or ORC/Open64 AFAICT. I actually expect more help from LLVM-friendly companies -- if only with suggestions, feedback and review comments :-) -- Marcel Moolenaar xcllnt at mac.com

On Jul 16, 2009, at 2:30 PM, Marcel Moolenaar wrote: > > BTW: I don't run Linux at all, so no Linux/ia64 support. > I can see how that could be a problem for people. > > Anyway: my case is a weak one and I would understand if the > target get axed without considering my email/request... Hi Marcel, There are two levels of problems with the IA64 backend. On the first

On May 24, 2008, at 4:25 PM, Marcel Moolenaar wrote: > On May 24, 2008, at 12:12 PM, Bill Wendling wrote: > >> Let us know if you would like extra eyes on the two PPC failures. >> Many >> of us have a lot of experience with C++. :-) Do you know where these >> allocations are? > > I don't mind if people help out, so here's some information: > Could