search for: pennware

Eli Friedman wrote: > 2009/8/2 Richard Pennington <rich at pennware.com>: >> The following fails on x86_64 because of the output constraint '0'. >> My question is, is this legal. LLVM complains about the size difference >> (32 vs 64), but it is the same register (ax). >> Works on x86. >> >> %42 = call i64 asm sideeffec...

2009/8/2 Richard Pennington <rich at pennware.com>: > Eli Friedman wrote: >> 2009/8/2 Richard Pennington <rich at pennware.com>: >>> The following fails on x86_64 because of the output constraint '0'. >>> My question is, is this legal. LLVM complains about the size difference >>> (32 vs 64),...

----- Original Message ----- > From: "Hal Finkel via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Richard Pennington" <rich at pennware.com> > Cc: llvm-dev at lists.llvm.org > Sent: Wednesday, September 7, 2016 7:37:50 AM > Subject: Re: [llvm-dev] [PowerPC] Recent branch too far breakage > > Hi Rich, > > It is hard to tell, but there was a bug fix made to the branch > relaxation code; perhaps the fix wa...

On Sat, May 17, 2008 at 11:34 AM, Richard Pennington <rich at pennware.com> wrote: > If I run the optimizer (opt) on this code snippet with -std-compile-opts > the optimizer hangs. > > > ; ModuleID = 'test.ubc' > target datalayout = > "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:1...

Hi, I know my last question was very vague (i.e. "It stopped working, what went wrong?"), so here is a little more concrete example: If I run the optimizer (opt) on this code snippet with -std-compile-opts the optimizer hangs. ; ModuleID = 'test.ubc' target datalayout =

Anyone mind if I add "x86" to Triple.cpp to match x86? I'd like to use the name x86 for consistency. -Rich

On Tue, Jul 28, 2009 at 5:35 AM, Richard Pennington<rich at pennware.com> wrote: > Anyone mind if I add "x86" to Triple.cpp to match x86? I would really rather you didn't. :) Triple is intended to match the "target triples", for example the autconf/config.guess type stuff. I really don't want to add to the genetic diversity of tha...

The following fails on x86_64 because of the output constraint '0'. My question is, is this legal. LLVM complains about the size difference (32 vs 64), but it is the same register (ax). Works on x86. %42 = call i64 asm sideeffect "syscall\0A\09", "={ax},0,{di},~{dirflag},~{fpsr},~{flags}"(i64 231, i64 %41) nounwind ; <i64> [#uses=2] -Rich

2009/8/2 Richard Pennington <rich at pennware.com>: > The following fails on x86_64 because of the output constraint '0'. > My question is, is this legal. LLVM complains about the size difference > (32 vs 64), but it is the same register (ax). > Works on x86. > > %42 = call i64 asm sideeffect "syscall\0A\09&qu...

On Sun, Aug 16, 2009 at 11:47 AM, Richard Pennington<rich at pennware.com> wrote: > Richard Pennington wrote: >> >> Hi, >> >> The enclosed patch preserves debug information about compilation units, >> functions, and line number information when doing bitcode linking. I'm not >> easily able to try this for non-bitcode link...

I've just started looking into code generation and have a newbie question: Is there enough information in the .td files to make a tool to automatically generate an assembler from them? Is a project like that in the works? -Rich

Quoting Richard Pennington <rich at pennware.com>: > I've just started looking into code generation and have a newbie > question: Is there enough information in the .td files to make a tool to > automatically generate an assembler from them? Is a project like that > in the works? > > -Rich Hi your question is rea...

Hi, Nikolaos Kavvadias wrote: > Quoting Richard Pennington <rich at pennware.com>: > > I've just started looking into code generation and have a newbie > > question: Is there enough information in the .td files to make a > > tool to automatically generate an assembler from them? Is a project > > like that in the works? > > your question...

Well, at least it works on some programs across all arches. That was some great testing you've done for us. :-) Thanks! Renato On 28 Oct 2016 23:51, "Richard Pennington" <rich at pennware.com> wrote: > On 10/28/2016 05:27 PM, Renato Golin wrote: > >> On 28 October 2016 at 23:02, Rui Ueyama via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >> >>> Awesome results! >>> >> I'm surprised! LLD is barely working on ARM at the...

...earch path (e.g. /usr/arm-linux-gnueabihf/include) 3. Compile with correct compiler/linker flags (e.g. -target arm-linux-gnueabihf and some cmake tricks) Feel free to let me know if you have encountered any problem. Sincerely, Logan On Tue, Sep 30, 2014 at 5:22 PM, Richard Pennington <rich at pennware.com> wrote: > On 09/30/2014 02:37 AM, gamma_chen wrote: > > The following web say the libc++abi is ready on arm. > http://libcxxabi.llvm.org/spec.html > > I try to build libc++ and libc++abi for host x86_64(linux) and target > arm(linux) but fail. > I have read the we...

...ore general in LLVM, rather than specifically in clang, so that other llvm tools (e.g. llvm-objdump) could take advantage of a similar format for target description files if they need something more than just the triple argument. David > On 15 Sep 2014, at 13:09, Richard Pennington <rich at pennware.com> wrote: > > I've updated my blog with the current state of my compilation configuration prototype. http://ellcc.org/blog/?p=13246 > Again, any comments/criticisms greatly appreciated. > > -Rich > > On 09/05/2014 09:23 PM, Richard Pennington wrote: >> A while...

Interesting. File please? Thanks. On Sep 21, 2013 6:01 AM, "Richard Pennington" <rich at pennware.com> wrote: > Hi, > > I just updated from r190763 to r191137 and started getting failures in > generated assembly language when debug info is enabled. Here is the test > case: > > // Compile and run for every target. > // RUN: %ecc -g -o %t %s && %t > // FAIL:...

On 12/21/07, Richard Pennington <rich at pennware.com> wrote: > I'm a little further along now. I've started to put together a simple > driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think > it works). Er. Hm. Can you explain the name? The problem with names like "ellsif" is that it...

...2013 11:26 AM > > Interesting. File please? Thanks. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > Richard Pennington <mailto:rich at pennware.com> > Saturday, September 21, 2013 5:52 AM > Hi, > > I just updated from r190763 to r191137 and started getting failures in > generated assembly language when debug info is enabled. Here is the > test case: > > // Compile and run for every target. > // RUN: %ecc -g...

A while back (2012) there were a few messages related to using YAML config files to set up how clang would build stuff, especially for cross compilers. My ELLCC project is entirely cross compilation focused, so today I decided to play around with the config file idea. Right now it only handles replacing a "-target foo" option with the options defined in the file foo in the