[roll] Roll fuchsia [rust][trace] Force inlining in trace events

fxr/1440480 Used a trait to allow both cstr and str types to be passed
into, however, that caused and extra function call in the hot path for
trace events. Fortunately, we know the types at compile time and can
inline them.

Before:
```
movq  %r15, %rdi
movq  %r13, %rsi
movq  %r14, %rdx
callq _RNvXs2_Cs9rL7iSpwbhI_13fuchsia_traceRNtNtNtCs9hKKWVkOsLP_4core3ffi5c_str4CStrNtB5_14CategoryString22acquire_context_cached@PLT
```

With inline, we get t he direct c-ffi call:
```
leaq  .Lanon.683d4762321e68041142f8877f91ac2c.3(%rip), %rdi
leaq  _RNvNCNCNvCs9PvRlR8danp_22trace_event_benchmarks4mains_005CACHE(%rip), %rsi
movq  %r13, %rdx
callq trace_acquire_context_for_category_cached@PLT
```
Original-Bug: 467764830

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1451534
Original-Revision: a16cc08792aa922b66954130611612660a03a4be
GitOrigin-RevId: 01e91c91bbcd21b910a3750bf44b099341654029
Change-Id: I9476e240a276f886e279b0fac360693eb5d82fac
1 file changed
tree: c7f1f0f4d9ae842b4268a4623e68aedcee62f664
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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.