public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/106998] [11/12/13/14 Regression] libsanitizer PATH_MAX not defined for linux new targets Date: Wed, 21 Feb 2024 05:05:15 +0000 [thread overview] Message-ID: <bug-106998-4-CEQb5yxI0j@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 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I looked upstream (both llvm and google/sanitizers) and don't see any bug filed. I looked into the musl sources, limits.h has the following line: e8b8f3c90 (Rich Felker 2011-06-25 15:38:00 -0400 47) #define PATH_MAX 4096 So this bug is invalid because musl's limits.h defines it and has had it defined since 2011 :).
prev parent reply other threads:[~2024-02-21 5:05 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 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 [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=bug-106998-4-CEQb5yxI0j@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: linkBe 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).