On Wed, Aug 17, 2005 at 12:53:14PM -0700, James E Wilson wrote:
> Alternatively, patches can be put into bugzilla bug reports. This will
> help make sure it won't get forgotten.
That's where we were headed, as mentioned at the end of a paragraph in
the email with the patch: "Once we're happy with
Erik Christiansen wrote:
> I've taken the liberty of cleaning up the L_callt_save_interrupt
> #ifdef, making it consistent with the following one for
> L_callt_save_all_interrupt. (This not only removes the .text error, but
> adopts the easier to handle layout of the latter.)
Patches should be sen
Torsten Mohr wrote:
> I wonder now how to proceed, do i need to report this stuff officially
> somewhere? I also got no answer to my mail from saturday morning,
> subject line "-mwarn-signed-overflow". I had to do that change to
> make gcc-3.4.4 compile.
gcc bugs can be reported into our bugzill
Hi,
> I've taken the liberty of cleaning up the L_callt_save_interrupt
> #ifdef, making it consistent with the following one for
> L_callt_save_all_interrupt. (This not only removes the .text error, but
> adopts the easier to handle layout of the latter.)
> Would you mind applying the attached pa
On Mon, Aug 15, 2005 at 07:55:00PM +0200, Torsten Mohr wrote:
> I wonder now how to proceed, do i need to report this stuff officially
> somewhere?
I've taken the liberty of cleaning up the L_callt_save_interrupt
#ifdef, making it consistent with the following one for
L_callt_save_all_interrupt.
Hi,
> To my untrained eye, this looks a little like a bug. In
> v850/lib1funcs.asm, .L_return_interrupt should IMHO be in the
> .call_table_text section, not .text. (Would you like to try making the
> change? It's still line 1459 in 3.4.4) We might be able to sneak in a
> fix before the experts ar
