public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/4417: struct copy calls memcpy with -ffreestanding
@ 2002-04-23 1:03 rth
0 siblings, 0 replies; 2+ messages in thread
From: rth @ 2002-04-23 1:03 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, robertlipe
Synopsis: struct copy calls memcpy with -ffreestanding
State-Changed-From-To: open->closed
State-Changed-By: rth
State-Changed-When: Tue Apr 23 01:03:18 2002
State-Changed-Why:
We've documented which functions libc must provide, and
memcpy is among them.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4417
^ permalink raw reply [flat|nested] 2+ messages in thread
* c/4417: struct copy calls memcpy with -ffreestanding
@ 2001-09-28 7:06 robertlipe
0 siblings, 0 replies; 2+ messages in thread
From: robertlipe @ 2001-09-28 7:06 UTC (permalink / raw)
To: gcc-gnats
>Number: 4417
>Category: c
>Synopsis: struct copy calls memcpy with -ffreestanding
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Sep 28 07:06:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Robert Lipe
>Release: 3.0.1
>Organization:
>Environment:
Any IA32 target, from what I can tell.
>Description:
-freestanding will, under some conditions, generate a call to
memcpy behind the back of the user. This defeats the point of
that flag
>How-To-Repeat:
typedef struct foo{
char blah[1024];
} foo_t;
extern foo_t one, two;
void
foo(void)
{
one = two;
}
$ cc -ffreestanding -O3 -S -o - a.c | grep memcpy
call memcpy
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-04-23 8:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-23 1:03 c/4417: struct copy calls memcpy with -ffreestanding rth
-- strict thread matches above, loose matches on Subject: below --
2001-09-28 7:06 robertlipe
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).