public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Danny Sadinoff <danny@sadinoff.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: middle-end/7898: [Sparc] readdir_r gives bad results with gcc-3.1 and 3.2 Date: Mon, 28 Apr 2003 20:26:00 -0000 [thread overview] Message-ID: <20030428202601.13449.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/7898; it has been noted by GNATS. From: Danny Sadinoff <danny@sadinoff.com> To: ehrhardt@mathematik.uni-ulm.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: middle-end/7898: [Sparc] readdir_r gives bad results with gcc-3.1 and 3.2 Date: Mon, 28 Apr 2003 16:25:16 -0400 Oh. Boy, that's egg on my face. Thanks for taking the time. On Mon, Apr 28, 2003 at 06:05:22PM -0000, ehrhardt@mathematik.uni-ulm.de wrote: > Synopsis: [Sparc] readdir_r gives bad results with gcc-3.1 and 3.2 > > State-Changed-From-To: open->closed > State-Changed-By: cae > State-Changed-When: Mon Apr 28 18:05:22 2003 > State-Changed-Why: > This is a user error. readdir_r expects a struct dirent with at least > NAME_MAX+1 characters allocated for d_name. However, declaring a normal > struct dirent will only give you only a single byte. > Besides none of this is under the control of gcc. > > regards Christian > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7898 >
next reply other threads:[~2003-04-28 20:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-28 20:26 Danny Sadinoff [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-28 18:05 ehrhardt
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=20030428202601.13449.qmail@sources.redhat.com \ --to=danny@sadinoff.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).