search for: plumhal

...ake complains GNUmakefile:16: /CoreOS/Standard/Standard.make: No such file or directory We started with a subversion checkout, in case it matters. --------------------------------------------------------------------+ Thomas Plum, Plum Hall Inc, 3 Waihona Box 44610, Kamuela HI 96743 USA tplum at plumhall.com .......... TEL +1-808-882-1255 FAX +1-808-882-1556 http://www.PlumHall.com .... TOLLFREE +1-800-PLUM-HALL (800-758-6425)

Hi Owen, Having looked into this due to Clang failing PlumHall with it recently I can give an opinion... I think !NoExcessFPPrecision covers FMA completely. There are indeed some algorithms which give incorrect results when FMA is enabled, examples being those that do floating point comparisons such as: a * b + c - d. If c == d, it is still possible for that...

On Feb 8, 2012, at 10:44 AM, James Molloy wrote: > Hi Owen, > > Having looked into this due to Clang failing PlumHall with it recently I can give an opinion... > > I think !NoExcessFPPrecision covers FMA completely. There are indeed some algorithms which give incorrect results when FMA is enabled, examples being those that do floating point comparisons such as: a * b + c - d. If c == d, it is still possibl...

...able to convert constpool entries as LLVM sees them into such instructions (see "doInitialPlacement"). Most of the complexity is in moving the constants around so that they're accessible from the instructions that use them, but for a first approximation that's not needed (beware, PlumHall's ch7_22 is a prime candidate for exercising this ability even with a 1MB range). Regards. Tim.

Hello everyone, I'd like to propose the attached patch to form FMA intrinsics aggressively, but in order to do so I need some clarification on the intended semantics for the various FP precision-related TargetOptions. I've summarized the three relevant ones below: UnsafeFPMath - Defaults to off, enables "less precise" results than permitted by IEEE754. Comments specifically

I am working towards a more complete solution for large constants in mips 16 (ala Arm constant islands and such). That is part of why I'm busy expanding all macros being emitted in the mips 16 compiler (almost done). I'm wondering if there is a poor mans approach for large constants that can be done very simply that I can add just for now. Gcc mips 16 places them after the function

...dual test was created / crafted with the same intent in mind (similar function size, number of functions, number of temporaries, etc). Most programmers don't pay that much attention to good code and end up writing horrible code, that stress specific parts of the compiler. If you have access to PlumHall suite, I encourage you to compile the chapter 7.22 test as an example. Also, related to register pressure, different bad codes will stress different algorithms, so you also have to be careful in stating that one algorithm is much better than others only based on one badly-written program. Ghass...

...; The ARM Holdings emulator does this; I used it with great success to > profile an Advanced Encryption Standard encryptor a while back. It is indeed a useful piece of kit. We do a lot of our internal regression tests on it, and also run LLVM's regression tests every night on it (as well as PlumHall, EEMBC and SpecInt). Unfortunately it's not exactly software we can give away or give access to. ________________________________________ From: Don Quixote de la Mancha [quixote at dulcineatech.com] Sent: 13 October 2011 18:47 To: Joe Abbey Cc: Renato Golin; rajav at codeaurora.org; llvmdev at...

...tools and technologies will further qualify this engineer: gdb gnu make bash perl python tcl autoconf m4 dejagnu expect mysql php linux git subversion Knowledge and experience with compiler internals and related tools is a plus, as is experience with MIPS or ARM architectures, and experience with plumhall or perennial test suites. To apply for this position, email resume to susan at mips.com<mailto:susan at mips.com>. MIPS Technologies is an equal opportunity employer and values your individuality. Susan Welch Senior Technical Recruiter MIPS Technologies 955 East Arques Avenue Sunnyvale,...

...l entries as LLVM sees them into such instructions > (see "doInitialPlacement"). > > Most of the complexity is in moving the constants around so that > they're accessible from the instructions that use them, but for a > first approximation that's not needed (beware, PlumHall's ch7_22 is a > prime candidate for exercising this ability even with a 1MB range). > > Regards. > > Tim. >

Hi Renato, Please see my answers below. Thanks -Ghassan ________________________________ From: Renato Golin <renato.golin at linaro.org> To: Ghassan Shobaki <ghassan_shobaki at yahoo.com> Cc: Andrew Trick <atrick at apple.com>; "llvmdev at cs.uiuc.edu" <llvmdev at cs.uiuc.edu> Sent: Thursday, September 19, 2013 5:30 PM Subject: Re: [LLVMdev] Experimental

...dual test was created / crafted with the same intent in mind (similar function size, number of functions, number of temporaries, etc). Most programmers don't pay that much attention to good code and end up writing horrible code, that stress specific parts of the compiler. If you have access to PlumHall suite, I encourage you to compile the chapter 7.22 test as an example. Also, related to register pressure, different bad codes will stress different algorithms, so you also have to be careful in stating that one algorithm is much better than others only based on one badly-written program. Ghass...

...rote: The ARM Holdings emulator does this; I used it with great success to profile an Advanced Encryption Standard encryptor a while back. It is indeed a useful piece of kit. We do a lot of our internal regression tests on it, and also run LLVM's regression tests every night on it (as well as PlumHall, EEMBC and SpecInt). Unfortunately it's not exactly software we can give away or give access to. ________________________________________ From: Don Quixote de la Mancha [quixote at dulcineatech.com<mailto:quixote at dulcineatech.com>] Sent: 13 October 2011 18:47 To: Joe Abbey Cc: Renato...

On Thu, Oct 13, 2011 at 10:00 AM, Joe Abbey <jabbey at arxan.com> wrote: > However, we don't have testing resources to test both our product and LLVM > on a host of target boards.  We have some chumbys, beagleboards, iPhones, > iPod Touches, tables, Android Phones, etc.  And most of those are already > booked solid with our own regression tests (most of which are based on

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

Admittedly we're very interested in becoming ARM backend maintainers as our product heavily relies on LLVM. However, we don't have testing resources to test both our product and LLVM on a host of target boards. We have some chumbys, beagleboards, iPhones, iPod Touches, tables, Android Phones, etc. And most of those are already booked solid with our own regression tests (most of which

John; I'm trying to flash 7.1. What I followwd was the wiki page you refer to. My real question is do I need the .load file tftp debug shows the 7960G is asking for? Voipsupply didn't supply it. I'm trying to verify that's what I need befor I start hounding them. -JB Hawaii John Bittner wrote: >John, > >You have to go to 7.1 before 7.3 >Also look at this.