public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ams at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/21706] MAXPATHLEN usage in [gcc]/gcc/tlink.c
Date: Thu, 26 May 2005 13:51:00 -0000 [thread overview]
Message-ID: <20050526125926.22204.qmail@sourceware.org> (raw)
In-Reply-To: <20050522121257.21706.ams@gnu.org>
------- Additional Comments From ams at gnu dot org 2005-05-26 12:59 -------
(In reply to comment #3)
> Like most POSIX limits PATH_MAX may not be defined if the actual limit is not
> fixed.
Correct, and GNU doesn't have such a limit for the length of filenames, the
number of arguments passed to a program or the length of a hostname. And
probobly a whole bunch of other things that have slipped my mind right now.
All of this is perfectly compliant with POSIX.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21706
next prev parent reply other threads:[~2005-05-26 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 12:13 [Bug c/21706] New: " ams at gnu dot org
2005-05-22 13:52 ` [Bug c/21706] " schwinge-bugzilla-gcc dot gnu dot org at nic-nac-project dot de
2005-05-22 14:04 ` [Bug middle-end/21706] " pinskia at gcc dot gnu dot org
2005-05-22 15:35 ` gdr at integrable-solutions dot net
2005-05-22 15:36 ` schwab at suse dot de
2005-05-26 13:51 ` ams at gnu dot org [this message]
2005-05-30 15:23 ` pinskia at gcc dot gnu dot org
2005-06-19 14:00 ` pinskia at gcc dot gnu 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=20050526125926.22204.qmail@sourceware.org \
--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).