On 10/26/22 03:34, Sebastian Huber wrote:
On 04/10/2022 11:47, Sebastian Huber wrote:
On 08/09/2022 07:33, Sebastian Huber wrote:
On 04/08/2022 15:02, Sebastian Huber wrote:
On 22/07/2022 15:02, Sebastian Huber wrote:
gcc/ChangeLog:
* gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined.
(CC1_SPEC): Define to SUBTARGET_CC1_SPEC.
* config/arm/arm.h (CC1_SPEC): Remove.
* config/arc/arc.h (CC1_SPEC): Append SUBTARGET_CC1_SPEC.
* config/cris/cris.h (CC1_SPEC): Likewise.
* config/frv/frv.h (CC1_SPEC): Likewise.
* config/i386/i386.h (CC1_SPEC): Likewise.
* config/ia64/ia64.h (CC1_SPEC): Likewise.
* config/lm32/lm32.h (CC1_SPEC): Likewise.
* config/m32r/m32r.h (CC1_SPEC): Likewise.
* config/mcore/mcore.h (CC1_SPEC): Likewise.
* config/microblaze/microblaze.h: Likewise.
* config/nds32/nds32.h (CC1_SPEC): Likewise.
* config/nios2/nios2.h (CC1_SPEC): Likewise.
* config/pa/pa.h (CC1_SPEC): Likewise.
* config/rs6000/sysv4.h (CC1_SPEC): Likewise.
* config/rx/rx.h (CC1_SPEC): Likewise.
* config/sparc/sparc.h (CC1_SPEC): Likewise.
Could someone please have a look at this patch set?
Ping
Would someone mind having a look at this patch set? If there is a
better approach to customize the default TLS model, then please let
me know.
It would be nice if someone could review the patch before the Stage 1
ends at November 13th.
Just a reminder. The guidelines are a patch needs to be posted before
the end of stage1 to make the deadline. Review & integration can happen
after the deadline.
I realize the idea here is to allow RTEMS to change the default TLS
model. But does it also happen to make it possible to solve Keith
Packard's issues with picolibc? See the Aug/Sep gcc-patches archives.
It looks sensible. I assume you did a "find" to identify all the
CC1_SPECs to change.
OK for the trunk,
Jeff
Anyway, does this also solve some of the issue Keith Packard was try to
nail down for picolibc?
