public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: awk@localhost.localdomain, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c/5351: function pass-by-value structure copy corrupts structure on stack Date: Tue, 05 Nov 2002 08:05:00 -0000 [thread overview] Message-ID: <20021105160553.548.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1026 bytes --] Synopsis: function pass-by-value structure copy corrupts structure on stack State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Tue Nov 5 08:05:52 2002 State-Changed-Why: I can reproduce this with 3.2.1pre, but it seems fixed in present CVS. However, since this is a regression w.r.t. 2.95, I leave it open and put it into "high". A reduced testcase is this: ---------------------------------- #include <stdio.h> #include <string.h> struct X { char s[100]; }; void foo(struct X x) { printf("x.s: %s\n", x.s); } int main() { struct X x; strcpy(x.s, "this is a test string"); foo(x); } ------------------------------------- With 3.2.1pre I get tmp/g> /home/bangerth/bin/gcc-3.2.1-pre/bin/gcc x.c tmp/g> ./a.out x.s: Äñÿ¿Ôa@st string This is not what I want to see. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5351
next reply other threads:[~2002-11-05 16:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-05 8:05 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-08 15:17 jbuck 2002-11-06 11:06 Wolfgang Bangerth 2002-01-10 10:56 Tony Knaus
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=20021105160553.548.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=awk@localhost.localdomain \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).