similar to: M68K codegen target

Hi Anton, Thanks for the tip. I’ve moved some common code from the patch: https://reviews.llvm.org/D50784 <https://reviews.llvm.org/D50784> https://reviews.llvm.org/D50856 <https://reviews.llvm.org/D50856> https://reviews.llvm.org/D50858 <https://reviews.llvm.org/D50858> but the backend itself is still quite large. Anything more I can do to simplify reviewing? > On 15 Aug

Hi All, We would like to contribute our supports for Motorola 68000 series CPU (also known as M68k or M680x0) into LLVM. And we want to hear feedbacks from you Here is some background for M68k: Motorola 68000 series CPU was one of the most popular CPUs used by personal computers in the ‘80, including some of the earliest Apple Macintosh. Fast-forwarding to modern days, M68k is still popular

Hello! Almost two years ago, Artyom Goncharov submitted an initial effort for a backend for the Motorola 68000 architecture [1] which was eventually not merged, unfortunately. I elaborated why I supported the idea of such a backend [2]. Recently, we started a fundraising campaign on the platform Bountysource.com to port the M68K backend in GCC to the new MODE_CC register representation which was

Hi I want to cross-compile llvm  for  arm board , running llvm on  Ububtu Server 11.04  x86_64  thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111017/178ae8fe/attachment.html>

Oops, I neglected to reply-all…. The current stable branch at github still has it: https://github.com/apple/swift-llvm/blob/stable/include/llvm/Support/ARMTargetParser.def#L106 <https://github.com/apple/swift-llvm/blob/stable/include/llvm/Support/ARMTargetParser.def#L106> Should I get the head of the non-swift repository and generate a new diff? Also, I suspect that it’s not a good idea

Thanks for the clarifications, Bob! I’ve spent some time with the head of the llvm.org repo, and I now understand a lot better what Renato and Tim were talking about re. the architecture aliases. The patch to add v6l, therefore, seems simple enough. I haven’t been able to test it in my usual flow, because that involves the whole swift stack. I’m considering creating a program that links to

Thank you very much for the references, we've missed this discussion from last week. Seeing that the RFC hasn’t got any new responses since Wed 12th, is now the time to declare that the community has accepted the proposal, and to update the docs? Or is there any formal deadline for objections to be raised? -----Original Message----- From: meinersbur at googlemail.com [mailto:meinersbur at

> You assume triples make sense. That's the first mistake everyone does > when thinking about triples. :) I know they don't make sense in many corner cases, but I think discarding logic where it *does* exist is a mistake. > AFAIK, "ARMv7B" is only used by HighBank, which is no more. But that, > too, was "ARMv7A big endian". I believe it's what any

Hello, About a month ago, I submitted a set of patches for review on llvm-commit. The most controversial of the patches, http://lists.cs.uiuc.edu/pipermail/llvm-commits/attachments/20150622/d104ea7 1/attachment-0009.obj deals with the fact that before ARMv8, the rGPR RegClass in Thumb encodings didn't include SP; but from ARMv8 onwards, it does include it. RegClass membership is

Taking the suggestions of the group under consideration, I’ve generated a new diff. The thing to note is that armv6l is now treated identically to armv6hl. I’ve also added a unit test. This seems to me to be the least invasive method, and holds to existing conventions as closely as possible. Thoughts? -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hi Everybody, I have a puppet setup working, but run into issue, which couldn''t figure out how to solve. Say I have puppet agent generated certificate and signed it on puppet master. If somehow puppet agent''s hostname has been changed it will stop communication with puppet master. I would like to know if there is a way to be able to change hostname of puppet agent, without

>> Going back through SVN history, I cannot find any evidence that ARMv6L ever existed. > > Oh, my bad!! I was thinking of ARMv7l... :/ > > Nevertheless, I'll leave you guys to review this one, as I lost touch with the parser a while ago. Ah, I see: ARMv7L is now an alias for ARMv7A. So, if William has to add support for ARMv6L, I'd suggest he adds it as an alias, and

include/llvm/Support/Casting.h:194: typename cast_retty<Instruction, Value *>::ret_type llvm::cast(llvm::Value *const &): Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed. 0 clang 0x00000000019867cf 1 clang 0x0000000001986ce9 2 libpthread.so.0 0x00007f6921e2f060 3 libc.so.6 0x00007f69211113a5 gsignal + 53 4 libc.so.6

I found a "feature" or a bug in metaflac (and possibly libflac) metadata handling. If you try to add some tags to file, and padding field is not big enough, padding size doesn't get increased automaticly, so you receive an error about corrupted file (tried both with foobar2k and metaflac). But if you previously add more padding with "--add-padding=", everything goes

This buildbot seems to have been failing for a while (though it's hard for me to identify the root cause in the logs, as I mentioned in another thread, so it's hard to say if it's the same failure, or if the failure is consistent, etc) - anyone watching it/caring aobut it? ---------- Forwarded message ---------- From: <llvm.buildmaster at lab.llvm.org> Date: Wed, Sep 30, 2015 at

Hello, http://llvm.org/docs/GettingStarted.html#software lists "GCC >=4.7.0" among requirements for building LLVM. However, my attempt of building LLVM+Clang with gcc 4.7.3 has failed with a multitude of errors, such as: lib/LTO/Caching.cpp:74:7: error: looser throw specifier for 'virtual llvm::lto::localCache(std::string, llvm::lto::AddFileFn)::<lambda(unsigned int,

>> However, because the DefaultTargetTriple is armv6l-unknown-linux-gnueabihf, >> and llvm didn’t know about v6l, it would fail to match and canonicalize to armv6. >> I added the notion of v6l to llvm to address this. > > ARMv6l was definitely there once. I'm not sure what happened. > > I'm copying the ARM folks that did most of the recent changes in hope

Samba - General mailing list wrote > On Wed, 17 May 2017 04:26:16 -0700 (PDT) > artyom via samba &lt; > samba at .samba > &gt; wrote: > >> I use official manual from wiki.samba.org for install samba 4.6.3 >> (from source) with bind_dlz on bind 9.9.10 (from source too). My OS >> is Debian Jessie x64 8.8 netinst. I use >>

Hi Artyom, please open a bugreport as suggested by clang: ... snipped ... > clang: note: diagnostic msg: Please submit a bug report to http://llvm.org/bugs/ > and include command line arguments and all diagnostic information. > clang: note: diagnostic msg: Preprocessed source(s) are located at: > clang: note: diagnostic msg: /tmp/sqlite3-8WsrrL.i Ciao, Duncan.

Hi, all! Does any body use this print station? I try print via smbspool or smbclient and every time I got "access denyed" error. # smbspool smb://ps786fba/Printer1 101 artem Test 1 - test.txt ERROR: ERRSRV - ERRaccess opening remote file Test # PIGGY$ smbclient //ps786fba/Printer1 -P added interface ip=192.168.9.250 bcast=192.168.9.255 nmask=255.255.255.0 Got a positive name query