--
What|Removed |Added
Target Milestone|--- |4.0.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23065
--- Additional Comments From tobi at gcc dot gnu dot org 2005-08-19 15:51
---
Fixed.
--
What|Removed |Added
CC||tobi at gcc dot g
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-08-19
15:50 ---
Subject: Bug 23065
CVSROOT:/cvs/gcc
Module name:gcc
Branch: gcc-4_0-branch
Changes by: [EMAIL PROTECTED] 2005-08-19 15:50:43
Modified files:
gcc/fortran: Change
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-08-19
09:05 ---
Subject: Bug 23065
CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED] 2005-08-19 09:05:03
Modified files:
gcc/fortran: ChangeLog gfortran.h module.c scanner
--- Additional Comments From Tobias dot Schlueter at physik dot
uni-muenchen dot de 2005-08-14 22:02 ---
Subject: Re: MAXPATHLEN usage in fortran/{scanner,module}.c
Steve Kargl wrote:
> The attached patches uses alloca to remove the use of PATH_MAX
> from gfortran. It also fixes one o
--- Additional Comments From pinskia at physics dot uc dot edu 2005-08-01
18:34 ---
Subject: Re: MAXPATHLEN usage in fortran/{scanner,module}.c
On Aug 1, 2005, at 2:26 PM, Steve Kargl wrote:
> On Mon, Aug 01, 2005 at 04:46:17PM -, pinskia at gcc dot gnu dot
> org wrote:
>>
>> We
--- Additional Comments From ams at gnu dot org 2005-08-01 18:24 ---
Subject: Re: MAXPATHLEN usage in fortran/{scanner,module}.c
>So, does GNU define _POSIX_PATH_MAX?
>
> No.
Then GNU isn't POSIX compliant.
Sorry, I meant yes. We do define _POSIX_PATH_MAX. My brain
--- Additional Comments From sgk at troutmask dot apl dot washington dot
edu 2005-08-01 18:13 ---
Subject: Re: MAXPATHLEN usage in fortran/{scanner,module}.c
On Mon, Aug 01, 2005 at 05:48:10PM -, ams at gnu dot org wrote:
>
> Subject: Re: MAXPATHLEN usage in fortran/{scanner,modu
--- Additional Comments From ams at gnu dot org 2005-08-01 17:48 ---
Subject: Re: MAXPATHLEN usage in fortran/{scanner,module}.c
So, does GNU define _POSIX_PATH_MAX?
No.
Does GNU support pathconf()?
Yes.
I read the other thread where it is suggested that a non-portable
G
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-01
16:46 ---
Well in both the cases in the fortran front-end, really an alloca should be
used instead of MAXPATHLEN.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23065
--- Additional Comments From kargl at gcc dot gnu dot org 2005-08-01 16:43
---
Posix says:
Pathname Variable Values
The values in the following list may be constants within an
implementation or may vary from one pathname to another. For
example, file systems or directories may
--- Additional Comments From schwinge-bugzilla-gcc dot gnu dot org at
nic-nac-project dot de 2005-08-01 11:07 ---
(In reply to comment #3)
> So, GNU does not follow IEEE Std 1003.1, 2004?
We do follow IEEE Std 1003.1, 2004 here, the standard does not mandate that
PATH_MAX _must_ be defi
--- Additional Comments From kargl at gcc dot gnu dot org 2005-07-25 21:41
---
So, GNU does not follow IEEE Std 1003.1, 2004?
gfortran.h contains
#include
#ifndef PATH_MAX /* This is defined in a IEEE Std 1003.1, 2004 */
# include
# define PATH_MAX MAXPATHLEN
#endif
-
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-25
20:43 ---
Never mind, it is indirect with PATH_MAX.
In fact this is a bad use of MAXPATHLEN because we could get a buffer overflow.
--
What|Removed |Added
14 matches
Mail list logo
