URL:
<http://savannah.gnu.org/task/?func=detailitem&item_id=5726>
Summary: GCC built-in functions
Project: The GNU Hurd
Submitted by: tschwinge
Submitted on: Monday 07/17/06 at 14:38
Category: GNU Mach
Should Start On: Monday 07/17/06 at 00:00
Should be Finished on: Monday 07/17/06 at 00:00
Priority: 1 - Later
Status: None
Privacy: Public
Assigned to: None
Percent Complete: 0%
Open/Closed: Open
Planned Release: GNU Mach 1.4
Effort: 0.00
_______________________________________________________
Details:
How to deal with GCC built-in functions?
22:52 <bddebian> We need prototypes for memcpy and memset in gnumach. It
would alleviate alot of build warnings.
22:53 <antrik> in the linux drivers or in gnumach itself?
22:54 <bddebian> gnumach itself
22:54 <bddebian> I'm trying to find a "global" header file to stick them in
:-)
22:55 <bddebian> port.h maybe
22:56 <antrik> do these functions exist anywhere in the source, or does it
rely on compiler builtins?...
22:56 <bddebian> They are implicetly defined in several programs
22:57 <bddebian> ipc_entry.c for example:
22:57 <bddebian> if (!it_entries_reallocable(oits))
22:57 <bddebian> (void) memcpy((void *) table, (const void *)
otable,
22:57 <bddebian> osize * sizeof(struct ipc_entry));
23:14 <bddebian> So, since all you guru's are here, what header file should I
put prototypes for memcpy and memset in? :-)
23:15 <marcus> oh you are writing an allocator? :)
23:15 <marcus> malloc.h
23:15 <marcus> oh
23:16 <neal> memcpy and memset are usually in string.h
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?func=detailitem&item_id=5726>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-hurd mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-hurd
