public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29576] librtld.os: in function `_dl_start_profile': (.text+0x9444): undefined reference to `strcpy'
Date: Mon, 19 Sep 2022 18:09:10 +0000	[thread overview]
Message-ID: <bug-29576-131-5ubl1bBJWE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29576-131@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Adhemerval Zanella from comment #5)
> (In reply to Tomas Kolda from comment #4)
> > Not a bug. I have set CFLAGS, CPPFLAGS, CXXFLAGX to use -O2 instead of -Os.
> 
> Ideally, we should support -Os as well. I think we should add a patch
> similar to the one to avoid libcalls [1] also to fix the possible strcpy
> call.
> 
> [1]
> https://patchwork.sourceware.org/project/glibc/patch/20220811121909.4110665-
> 1-adhemerval.zanella@linaro.org/

I agree. If we get this clean I'll talk to DJ about cloning the CI builder and
test with -Os for pre-commit CI.

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

  parent reply	other threads:[~2022-09-19 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 15:39 [Bug build/29576] New: " koldat at gmail dot com
2022-09-16 15:41 ` [Bug build/29576] " koldat at gmail dot com
2022-09-17 15:35 ` carlos at redhat dot com
2022-09-19  6:44 ` koldat at gmail dot com
2022-09-19  6:46 ` koldat at gmail dot com
2022-09-19 14:07 ` adhemerval.zanella at linaro dot org
2022-09-19 18:09 ` carlos at redhat dot com [this message]
2022-10-09 14:55 ` romain.naour at gmail dot com
2022-10-09 22:09 ` adhemerval.zanella at linaro dot org
2022-12-29 13:00 ` adhemerval.zanella at linaro dot org

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-29576-131-5ubl1bBJWE@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).