[roll] Roll fuchsia [superproject] Roll llvm-project/libc [libc][setjmp] fix setjmp test via naked fn attr (#88054)

This would consistently fail for me locally, to the point where I could not run
ninja libc-unit-tests without ninja libc_setjmp_unittests failing.

Turns out that since I enabled -ftrivial-auto-var-init=pattern in
commit 1d5c16d ("[libc] default enable -ftrivial-auto-var-init=pattern
(#78776)")
this has been a problem. Our x86_64 setjmp definition disabled -Wuninitialized,
so we wound up clobbering these registers and instead backing up
0xAAAAAAAAAAAAAAAA rather than the actual register value.

Use `naked` function attribute to avoid function prolog/epilog.

GitOrigin-RevId: 1df12167ef62a4e075933b414a85254f9fbd9279
Original-Revision: fcb1d5a948da164d663abe34ca918bce8402d463
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1138260
Original-Revision: dc09938e6da583b3e3e1e911245c89071610fd35
Change-Id: I7d686c5b89c2a39ae249a349bc3c52af513065bb
1 file changed
tree: d5c4b6da51556934908a3e5ae9474c0a7b4f0423
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.