llvm dev - Jun 2017 - Question

Can you also please tell me how can I find out the ABI (application binary
interface)?
Thanks,Iulia
 

    On Monday, June 5, 2017 8:58 PM, Bruce Hoult <bruce at hoult.org>
wrote:
 

 grep name /proc/cpuinfo

Then look up the model number in
https://en.wikipedia.org/wiki/List_of_Intel_Xeon_microprocessors
On Mon, Jun 5, 2017 at 8:41 PM, Iulia Stirb via llvm-dev <llvm-dev at
lists.llvm.org> wrote:

Hello,
1. Can you please tell me how can I find the type of my Intel Xeon?I see in LLVM
code that Intel Xeon processors can be of type "core2",
"penryn", "westmere", "skylake".
2. I also see that "skylake" can be a type and a subtype as well.How
can I find out the subtype of my architecture?
Looking forward for you answer. Thank you.Iulia 

    On Sunday, June 4, 2017 7:11 PM, Tim Northover <t.p.northover at
gmail.com> wrote:
 

 Hi Lulia,

On 4 June 2017 at 08:39, Iulia Stirb via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Does LLVM support code generation for Intel Processors? Which Intel
> processors are supported? I am interested especially in Intel Xeon
> Processor, but you can give me information about the others as well.
Yes, x86 output is supported. "Xeon" is just a brand name for
Intel's
server chips though, and covers lots of very different CPUs going back
many years.

LLVM distinguishes them by which instructions the CPU supports, which
is mostly determined by which generation the chip is. You may have
heard names like "Haswell", "Skylake", "Canonlake"
mentioned; and
those are what LLVM uses to choose what you're compiling for. For
example if you know your Xeon is a Skylake one you'd specify
"-mcpu=skylake" (or an equivalent via the C++ API if you're
writing
your own compiler).

LLVM is capable of generating code for all of them, though some may
have had more tuning work for performance.

Cheers.

Tim.


   
______________________________ _________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org
http://lists.llvm.org/cgi-bin/ mailman/listinfo/llvm-dev





   
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170605/ad1aa80a/attachment.html>

On 5 June 2017 at 11:54, Iulia Stirb <iulia_s24 at yahoo.com>
wrote:
> Can you also please tell me how can I find out the ABI (application binary
> interface)?
Could you send your messages with a smaller font, or better still in
plain text? It's very distracting and quite difficult to read
(particularly your message about the errors MSVC was giving).

Anyway, your ABI will be determined by which OS you're compiling for
in almost all cases. And if you're building Clang on the same platform
you're running the binaries on that should be correctly detected when
you run CMake.

Otherwise you'll have to set the LLVM_DEFAULT_TARGET_TRIPLE CMake
variable. Typical values are "x86_64-linux-gnu",
"x86_64-apple-macosx10.12" or "x86_64-windows-msvc". That
will also
set the corresponding ABI.

Cheers.

Tim.

Thank you. So the ABI in llvm will be "gnu" for all Linux
distributions?

    On Monday, June 5, 2017 11:39 PM, Tim Northover <t.p.northover at
gmail.com> wrote:
 

 On 5 June 2017 at 11:54, Iulia Stirb <iulia_s24 at yahoo.com>
wrote:
> Can you also please tell me how can I find out the ABI (application binary
> interface)?
Could you send your messages with a smaller font, or better still in
plain text? It's very distracting and quite difficult to read
(particularly your message about the errors MSVC was giving).

Anyway, your ABI will be determined by which OS you're compiling for
in almost all cases. And if you're building Clang on the same platform
you're running the binaries on that should be correctly detected when
you run CMake.

Otherwise you'll have to set the LLVM_DEFAULT_TARGET_TRIPLE CMake
variable. Typical values are "x86_64-linux-gnu",
"x86_64-apple-macosx10.12" or "x86_64-windows-msvc". That
will also
set the corresponding ABI.

Cheers.

Tim.


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170606/8a18314c/attachment.html>