public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alex.fan.q at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29749] New: clarify usage of .cfi_label in riscv start.S
Date: Fri, 04 Nov 2022 11:20:58 +0000	[thread overview]
Message-ID: <bug-29749-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29749
           Summary: clarify usage of .cfi_label in riscv start.S
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: alex.fan.q at gmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

riscv's start.S includes a `.cfi_label dummy` directive in [1]. The comment
above it says 
> use a dummy .cfi_label to force starting the FDE.`
but as I understand it, `ENTRY (ENTRY_POINT)` macro includes a
`.cfi_startproc`, which should already do the same thing as comment suggests.

This directive was introduced in
https://sourceware.org/bugzilla/show_bug.cgi?id=23125 , but the original patch
in the first comment didn't include cfi_label and works as reported.

Zig compilation gets stuck on this directive as clang doesn't support it [2].

Can I get some help to clarify this directive and whether it is okay to remove
it?

[1]
https://github.com/bminor/glibc/blob/8c77e26ba8b360c851b2b9485bb4431aacc51ad1/sysdeps/riscv/start.S#L48
[2] https://github.com/ziglang/zig/issues/3340

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

             reply	other threads:[~2022-11-04 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 11:20 alex.fan.q at gmail dot com [this message]
2022-11-04 11:23 ` [Bug libc/29749] " alex.fan.q at gmail dot com
2022-11-04 11:31 ` alex.fan.q at gmail dot com
2022-11-05  5:15 ` alex.fan.q at gmail dot com
2022-11-08 15:38 ` schwab@linux-m68k.org
2022-11-11 13:16 ` alex.fan.q at gmail dot com

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-29749-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).