Message ID | 20180628084329.22754-3-rv@rasmusvillemoes.dk |
---|---|
State | New |
Headers | show |
Series | some vxworks/powerpc patches | expand |
On 2018-06-28 10:43, Rasmus Villemoes wrote: > In order to allow ZCX on VxWorks, we need the frame_dummy function to do > the register_frame_info(). So make sure crtbegin.o and crtend.o are > available for use with a custom spec file. Hi Olivier Can I also have your explicit ok for patch 2/4 (I'll fix the changelog as for the other patches)? Thanks, Rasmus
Hi Rasmus, > On 16 Aug 2018, at 11:30, Rasmus Villemoes <rv@rasmusvillemoes.dk> wrote: > > On 2018-06-28 10:43, Rasmus Villemoes wrote: >> In order to allow ZCX on VxWorks, we need the frame_dummy function to do >> the register_frame_info(). So make sure crtbegin.o and crtend.o are >> available for use with a custom spec file. > > Hi Olivier > > Can I also have your explicit ok for patch 2/4 (I'll fix the changelog > as for the other patches)? Yes, this is fine. We're working on a possible replacement of those crt files for VxWorks. Just not quite ready yet and no reason to block the current ones in the interim. Olivier
diff --git a/libgcc/config.host b/libgcc/config.host index 18cabaf24f6..3466ba70f27 100644 --- a/libgcc/config.host +++ b/libgcc/config.host @@ -1129,6 +1129,7 @@ powerpc*-*-linux*) ;; powerpc-wrs-vxworks*) tmake_file="$tmake_file rs6000/t-ppccomm rs6000/t-savresfgpr t-fdpbit" + extra_parts="$extra_parts crtbegin.o crtend.o" ;; powerpc-*-lynxos*) tmake_file="$tmake_file rs6000/t-lynx t-fdpbit"