mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: 王洪亮 <wanghongliang@loongson.cn>
Cc: musl@lists.openwall.com
Subject: Re: [musl] A question about if crti.s and crtn.s is not necessary?
Date: Wed, 09 Nov 2022 13:13:59 +0100	[thread overview]
Message-ID: <87y1ske35k.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20221109114854.GD98588@port70.net> (Szabolcs Nagy's message of "Wed, 9 Nov 2022 12:48:54 +0100")

* Szabolcs Nagy:

> * 王洪亮 <wanghongliang@loongson.cn> [2022-11-09 10:51:37 +0800]:
>> In LoongArch port, I found build musl and libc-test is OK without
>> crt/loongarch64/crti.s and crt/loongarch64/crtn.s,
>> 
>> so I want to ask if crti.s and crtn.s is not necessary in architecture?
>
> in musl the generic crti/crtn.o is empty.
> which works if no user code uses .init or .fini sections.
>
> the old way of doing ctors/dtors used .init/.fini but new targets use
> .init_array/.fini_array for a while now.
>
> if no language feature uses .init/.fini, should we support this?

New architectures are supposed to not use DT_INIT/DT_FINI (in glibc
terms, ELF_INITFINI is defined as 0) because they have been deprecated
in the toolchain for a long, long time.

Thanks,
Florian


      reply	other threads:[~2022-11-09 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  2:51 王洪亮
2022-11-09 11:48 ` Szabolcs Nagy
2022-11-09 12:13   ` Florian Weimer [this message]

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=87y1ske35k.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=musl@lists.openwall.com \
    --cc=wanghongliang@loongson.cn \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).