This is the mail archive of the newlib@sources.redhat.com mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA:] Fix libgloss/d30v/syscalls.c



I am starting to wade through some targets and wanted
to make sure I did it the right way.

Is there any standard on what we want on the right hand
side?  I see Hans is tab'ing out a few and then putting
\n\.  

Hans.. do you have an order you are working through the
files in?  I want to work on a different subset than you.

How are you testing before you submit your patches?  

I want to do things the same way everyone else is and
avoid duplicate work. :)

FYI I have email from someone doing the xscale
directory so we can avoid that one.

--joel

Hans-Peter Nilsson wrote:
> 
> Another one.  Including sys/types.h is necessary because of
> time_t.  Note that d30v-elf ICE:s in libstdc++-v3 at the moment
> in GCC CVS head, but at least it gets beyond this point with
> this patch.  (Please don't CC me discussions about multi-line
> strings as such, sorry.)
> 
> 2002-04-15  Hans-Peter Nilsson  <hp@bitrange.com>
> 
>         * d30v/syscalls.c: #include <sys/types.h>.  Don't use multi-line
>         strings.
> 
> brgds, H-P
> 
>   ------------------------------------------------------------------------
>                 Name: sysc1b
>    sysc1b       Type: Plain Text (TEXT/PLAIN)
>             Encoding: BASE64
>          Description: syscalls.c.patch

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]