public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/106998] [10/11/12/13 Regression] libsanitizer PATH_MAX not defined for linux new targets
Date: Wed, 22 Feb 2023 01:46:37 +0000 [thread overview]
Message-ID: <bug-106998-4-6EIao6CKzD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106998-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106998
--- Comment #4 from cqwrteur <unlvsur at live dot com> ---
(In reply to Richard Biener from comment #3)
> I don't see linux/limits.h included still, but limits.h is - should musl
> include linux/limits.h by itself?
>
> Please link to upstream generated issues.
musl does not even want you to detect anything. There is not even __musl__
macro
next prev parent reply other threads:[~2023-02-22 1:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 16:39 [Bug sanitizer/106998] New: " unlvsur at live dot com
2022-09-22 17:37 ` [Bug sanitizer/106998] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-12-22 14:37 ` rguenth at gcc dot gnu.org
2023-02-21 13:55 ` rguenth at gcc dot gnu.org
2023-02-22 1:46 ` unlvsur at live dot com [this message]
2023-03-27 13:56 ` rguenth at gcc dot gnu.org
2023-07-07 10:44 ` [Bug sanitizer/106998] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-02-21 5:05 ` pinskia at gcc dot gnu.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-106998-4-6EIao6CKzD@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).