public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i at maskray dot me" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/26558] New: [meta] Build glibc with LLD
Date: Mon, 31 Aug 2020 23:19:30 +0000	[thread overview]
Message-ID: <bug-26558-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26558

            Bug ID: 26558
           Summary: [meta] Build glibc with LLD
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: i at maskray dot me
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

Some known issues:

* elf/librtld.map.o uses a subtle property of --defsym:
https://sourceware.org/pipermail/libc-alpha/2020-April/112732.html
* ld.lld --verbose does not print a linker script and ld.lld
--print-output-format is not supported:
https://sourceware.org/pipermail/libc-alpha/2020-April/112733.html
* Neither clang nor LLD may support the semantics of .tls_common
https://sourceware.org/pipermail/libc-alpha/2020-April/112734.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-08-31 23:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 23:19 i at maskray dot me [this message]
2020-08-31 23:31 ` [Bug libc/26558] " i at maskray dot me
2020-09-01 12:41 ` hjl.tools at gmail dot com
2020-09-01 13:08 ` hjl.tools at gmail dot com
2020-09-01 14:25 ` hjl.tools at gmail dot com
2021-09-06  4:40 ` i at maskray dot me
2021-09-06  4:41 ` i at maskray dot me

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=bug-26558-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).