public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: libc-help <libc-help@sourceware.org>
Subject: Re: Best reference for understanding ELF format
Date: Tue, 20 Apr 2021 12:39:26 -0400	[thread overview]
Message-ID: <CAH8yC8=5f2vbP4NtHs6Zt2tTQnJG60z2Pdbep4QZ404iiQvr4w@mail.gmail.com> (raw)
In-Reply-To: <CABrM6wmXAu8ff=yOgGZzcG8THjuyTkRToSXNQ+AJ-Txg5hq72w@mail.gmail.com>

On Tue, Apr 20, 2021 at 12:29 PM Peng Yu via Libc-help
<libc-help@sourceware.org> wrote:
> ...
> People don't usually directly call ld to generate object, executable
> or shared library files.
>
> Instead, gcc/clang are called. So there is nothing wrong to say those
> files are produced by gcc/clang, at least at a superficially level.
> You can say that gcc/clang don't directly produce the ELF files.
> Nevertheless, this doesn't add too much to the topic of this thread.

I think Clang can produce object files directly. Clang has an
integrated assembler.

On OS X, sometimes you need to use -Wa,-q to enlist the Clang
Integrated Assembler because GNU toolchain is too old to consume code
for some ISA's, like AVX and AVX2. (That's assuming you're using a
modern GCC, like from Macports or Homebrew). That's why -Wa,-q shows
up in places like
https://github.com/weidai11/cryptopp/blob/master/GNUmakefile#L109.

Jeff

  reply	other threads:[~2021-04-20 16:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  3:38 Peng Yu
2021-04-16  3:47 ` Mike Frysinger
2021-04-17 12:31   ` Peng Yu
2021-04-19  7:29     ` Szabolcs Nagy
2021-04-19  7:53       ` Florian Weimer
2021-04-20  1:58       ` Peng Yu
2021-04-20  7:08         ` tomas
2021-04-20 13:19         ` Mike Frysinger
2021-04-20 13:40           ` Peng Yu
2021-04-20 14:18             ` Mike Frysinger
2021-04-20 15:12               ` Peng Yu
2021-04-20 16:39                 ` Jeffrey Walton [this message]
2021-04-20 16:51                   ` Carlos O'Donell
2021-04-21  3:19                     ` Peng Yu
2021-04-20 17:55                   ` Mike Frysinger
2021-04-20 18:01                 ` Mike Frysinger
2021-04-20  8:14     ` Jeffrey Walton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8yC8=5f2vbP4NtHs6Zt2tTQnJG60z2Pdbep4QZ404iiQvr4w@mail.gmail.com' \
    --to=noloader@gmail.com \
    --cc=libc-help@sourceware.org \
    --cc=pengyu.ut@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).