similar to: Automake Assembler Assumptions with LLVM-MC

On Wed, May 18, 2016 at 01:10:50PM +0000, Daniel Sanders via llvm-dev wrote: > It's my understanding that llvm-mc is intended to be a testing tool > for LLVM developers rather than an assembler for end users. Users > should be assembling with clang. Not all LLVM users are clang users. For example, we're using LLVM to build OpenVMS cross-compilers to x86 for our porting effort.

I think I've gotten FLAC__lpc_restore_signal() about as good as I'm going to get it. Here's what I have: -a new file, lpc_asm.s, which has the assembly routines -changes to cpu.h, cpu.c, and stream_decoder.c to enable them -changes to configure.in to support the new cpu stuff -a preliminary Makefile.am -maybe something else I'm forgetting Now automake complains that configure.in

I agree with David's sentiment. The second method appears to be easier to follow. IMHO, this would be easier for external users that desire to modify the backend for their own custom extensions/instructions. On Fri, Aug 18, 2017 at 5:05 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk > wrote: > On 18 Aug 2017, at 10:55, Alex Bradbury <asb at asbradbury.org> wrote: >

All, in working through the RISCV LLVM backend, I’m running into some trouble in defining the instruction formats for the system instruction. The system instructions follow a pre-defined instruction template (type-I), but differ in that they have no input registers (only the target). The system instructions are defined as: rdcycle Rt I’ve defined a stand-alone instruction definition (as

On 03/10/2014 06:56 PM, Ralph Giles wrote: > On 2014-03-10 2:47 PM, Jonathan Lennox wrote: >> If I add --disable-asm to the build, it builds correctly. >> >> Does anyone have experience with Apple assembler directives to know >> what?s the best way to fix this? I assume the Perl script to generate >> the assembler file is going to need to be modified somehow. >

----- Original Message ----- > From: "Sebastian Pop" <spop at codeaurora.org> > To: "James H Cownie" <james.h.cownie at intel.com> > Cc: "Hal Finkel" <hfinkel at anl.gov>, "John Leidel (jleidel)" <jleidel at micron.com>, "LLVM Dev" > <llvm-dev at lists.llvm.org>, "cfe-dev" <cfe-dev at

Hi, On Wed, Nov 11, 2015 at 8:01 AM, Cownie, James H via cfe-dev <cfe-dev at lists.llvm.org> wrote: > It would be much more convenient for those of us who are in town for SC and staying downtown if we could find somewhere in walking range. (Which in my mind is 1 to 3/2 of a mile; others may have different criteria, but I find a 30 min walk refreshing after taking beer :-). > Agreed.

Hi everyone, There seems to be a good level of interest in this; so we should settle on a time and location. It has been pointed out that previous socials were held at http://bbrovers.com/ - we seem to have a preference for the availability of alcoholic beverages, and otherwise no strong opinions have been expressed. Logistically, we should pick someplace likely to have flexibility regarding

# Summary As a consequence of comparing the RISC-V LLVM MC assembler to the RISC-V GNU assembler I've noticed that a number of targets have quite different handling for pc-relative jumps/branches with immediate integer operands in llvm-mc vs GNU as. I'll admit that this isn't likely to occur in hand-written code (as you'd almost always prefer to use a label), but thought it was

Josh, Automake 1.10 on OSX is giving me warnings like the following: test/Makefile.am:50: wildcard *.raw: non-POSIX variable name test/Makefile.am:50: (probably a GNU make extension) test/Makefile.am:50: wildcard *.flac: non-POSIX variable name test/Makefile.am:50: (probably a GNU make extension) test/Makefile.am:50: wildcard *.oga: non-POSIX variable name

Hearing no opinions to the contrary, let's say Banger's 6pm (tomorrow). Address and web site below. I submitted online for a reservation early this morning, and I'll try to get an updated head count on Sunday morning. -Hal Sent from my Verizon Wireless 4G LTE DROID On Nov 14, 2015 11:21 AM, Chandler Carruth <chandlerc at google.com> wrote: Did this ever get settled? On Fri,

I am using the source distribution, and the first puzzle is that it doesn't seem to match with the installation instructions from svn. E.g., svn talks about llvm, cfe, compiler-rt, etc; however, the source is in many differently named *.tar.gz files: clang-3.4.src.tar.gz libcxx-3.4.src.tar.gz polly-3.4.src.tar.gz clang-tools-extra-3.4.src.tar.gz lld-3.4.src.tar.gz

On 21 August 2017 at 11:53, Daniel Sanders <daniel_l_sanders at apple.com> wrote: > One thing to be aware of with this is that (IIRC) tablegen uses the pattern to infer things about the pattern. One example I vaguely remember is that an empty pattern would result in the same effect as hasSideEffects=1 and I think there were others. Thanks for the note - excellent point. Looking at

Hi John, Thank you for the comments. I am addressing some of them bellow. Regards, Samuel 2014-08-11 9:36 GMT-04:00 John Leidel (jleidel) <jleidel at micron.com>: > Sergey [et.al], thanks for putting this proposal together. Overall, this > looks like a pretty solid approach to providing relatively hardware > agnostic omp target functionality. I had several comments/questions

Hello again, Because the LLVM in HPC workshop will be in Austin on Nov. 15th (http://llvm-hpc2-workshop.github.io/), we'll have an anomalously-high density of LLVM developers in Austin that day. I think it would be a great evening to have an LLVM social! I'm not familair with the Austin area, but I've cc'd some folks who are (or at least were) in Austin, so hopefully we can get

Let me see if I understand the response ;-) When you are saying integrated assembler do you mean llc --filetype=obj? If so, we currently have that for an option when running the test-suite. When you say that to test the llvm-mc assembler for your target you don't substitute the gcc assembler invocation for llvm-mc which would expect the resultant executable run to pass. Instead you have to

I must not be asking clearly. I have a machine on which I have placed the tarballs - but no internet access. How do I use the *src.tar.gz files from the llvm 3.4 downloads page? I understand the layout produced by the svn actions, but if I have just the tarballs, do I simply replace "svn co" with "tar -xvzf" in the sequence? How do the names of the tarballs map to the names

Hi, There is no change in the compiler flags. I'm using as it is from the original code. No change in the Makefile and I believe it is using the floating point only by default. We are using 8k samples and mono so the commands is as follows. [root at MEDIA opus-1.1]# ./opus_demo -d 8000 1 opus_encoded_crash.opus opus_encoded_crash.pcm *And segmentation is as below..*. ............ Calling

> On 2/6/19 11:44 AM, Joakim Tjernlund wrote: > > On Wed, 2019-02-06 at 11:34 -0800, H. Peter Anvin wrote: > > > > Great, that tree now against a somewhat old gnu-efi though. > > > > To build against >= 3.0.8 I need to do: > > #gnu-efi >= 3.0.8 has memset/memcpy defined causing multiple syms errors > > sed -i 's/LDFLAGS =/LDFLAGS =

----- Original Message ----- > From: "Alex Bradbury" <asb at asbradbury.org> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Dev" <llvm-dev at lists.llvm.org>, "flang-dev" <flang-dev at googlegroups.com>, "Rob Neely" <neely4 at llnl.gov>, > "douglas miles (PGI)" <douglas.miles at