This is the mail archive of the ecos-patches@sources.redhat.com mailing list for the eCos 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: [openrisc] eCos & gcc bug


[ openrisc list de-CC'd ]

Robert Cragie wrote:
I have 'attached' a couple of patches. Run 'patch -p0 < <patchfile>' in the
following directories for each respective <patchfile>. I haven't put MIME
attachments on as they can be rejected by mailing lists. Snip the code
between the <<patchfile>> and </<patchfile>> brackets to get the
'attachments':

packages/language/c/libc/time/current/include:
language_c_libc_time_include.patch
packages/language/c/libc/time/current/src:
language_c_libc_time_src.patch

There is an issue in that I have changed a header file. I did a look to see
if anything called cyg_libc_time_itoa() and AFAICT nothing did.

Actually look at ecos/packages/language/c/libc/time/current/include/time.inl to see where it's used, although it should be benign, albeit possibly with a warning.


I am not suggesting that these patches should be permanent but they will get
a build going without resorting to knocking bits out and may help identify
the real problem in the toolset.

Not surprisingly I'm a little reluctant to apply a patch in generic code just because of a toolchain bug. Is it likely this toolchain bug would be fixed soon? Has someone checked if it's fixed in more recent GCC?


If it really won't be for a while, then I'll apply the patch since it is pretty benign. Once you send a new patch including time.inl and a ChangeLog entry anyway ;-).

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


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