> From: Joern Rennecke [mailto:joern.renne...@embecosm.com]
> Sent: Sunday, November 02, 2014 4:34 PM
>
> Sorry for the late reply, I was on vacation, and then I meant to flesh
> out a suitable
> solution for the macro/hook problem to test it, but the more I think
> about it, the more
> questions
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On
> Behalf Of Joseph S. Myers
>
> I'm not clear if you're proposing such a patch for review, but note:
Yep but not yet for inclusion as I'm waiting to see if this would suit the use
case of avr people.
>
> (a) you mean DEF_EXT_LIB_B
Hi all,
I changed the target hook somehow so that more code run in the backend since
depending on the target (avr-libc Vs newlib) two different schemes are used:
printf -> iprintf renaming or defining _printf_float as a global symbol.
I thus renamed the target hook to match such a usage.
The pr
> From: Joseph S. Myers [mailto:jos...@codesourcery.com]
> Sent: Tuesday, September 02, 2014 11:29 PM
>
> Identifiers beginning with a single underscore are reserved with file
> scope. This means an application cannot provide an external definition of
> them, because such an external definition w
> -Original Message-
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf
> Of Thomas Preud'homme
> Sent: Saturday, August 30, 2014 12:27 PM
> Mmmh indeed. I checked C99 and section 7.1.3 paragraph 1 third clause
> states:
>
> "
> From: Grissiom [mailto:chaos.pro...@gmail.com]
> Sent: Friday, August 29, 2014 11:51 PM
>
> Yes, it does. The namespace reserved for the implementation is _[_A-Z].
> The namespace _[a-z] is still available for the user. Which means the
> user can declare their own _printf_float, and WE (as th
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com]
> Sent: Thursday, August 28, 2014 9:48 PM
> >
> > Right now I'm having trouble to define stdio_altname in newlib-c.c since
> this would
> > require it to be a C target hook but such a hook cannot be called from
> middle end.
>
> Hmm, yes,
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com]
> Sent: Wednesday, August 27, 2014 7:54 PM
>
> Well, my goal was to have the selection be automatic for most use cases.
> That you can do a manual selection by providing -u / -l arguments to the
> linker is pretty much a given.
> Hmm, ins
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com]
> Sent: Wednesday, August 27, 2014 6:13 PM
>
> I don't see how it can be any other way. We want to be able to compile
> translation units individually, and then let the linker sort out if we need
> the
> floating point enabled implement
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com]
> Sent: Tuesday, August 26, 2014 6:44 PM
>
> Due to the library order defined in the specs, the float-enbled printf
> definition will
> be picked up from libprintf_flt.a .
It seems to me that it relies heavily on how symbol resolution wo
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com]
> Sent: Thursday, August 14, 2014 4:52 PM
>
> So my idea is to make the compile emit special calls when there are no
> floating
> point arguments. A library that provides the floating point enabled
> *printf/*scanf
> precedes libc in lin
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com]
> Sent: Thursday, August 14, 2014 4:52 PM
>
> Newlib also has an integer-only printf implementation, but in this case,
> the default is the other way round - you have to use functions with
> nonstandard
> names to use the integer-only imp
12 matches
Mail list logo
