[GCDAProfiling] Suppress -Wprio-ctor-dtor for GCC>=9 and remove unuse… #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d write_string/length_of_string The `__attribute__((destructor(100)))` diagnostic does not have a warning option in GCC 8 (before r264853) and thus cannot be suppressed. -- ported from llvm/llvm-project fix: llvm@1cfde14 https://bugs.llvm.org/show_bug.cgi?id=47399 (Fixes problem behind rust-lang/rust#76224)
|
@cuviper - Here's a PR to bring the llvm-project destructor priority fix into Rust's fork. Hopefully I followed the procedures correctly. Thanks! |
|
Thanks! |
|
The next step is a submodule update on rust-lang/rust. You could repurpose your other PR if you like. |
|
Working on that now. Thanks again. |
richkadel
added a commit
to richkadel/rust
that referenced
this pull request
Sep 4, 2020
|
(Sorry, I did create a separate PR. I'll abandon the original PR after the new one merges.) |
Dylan-DPC-zz
pushed a commit
to Dylan-DPC-zz/rust
that referenced
this pull request
Sep 5, 2020
…ority, r=cuviper Update llvm-project to include PR 73 rust-lang/llvm-project#73 r? @cuviper
richkadel
added a commit
to richkadel/rust
that referenced
this pull request
Sep 5, 2020
Dylan-DPC-zz
pushed a commit
to Dylan-DPC-zz/rust
that referenced
this pull request
Sep 5, 2020
…ority, r=cuviper Update llvm-project to include PR 73 rust-lang/llvm-project#73 r? @cuviper
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Sep 6, 2020
…ity, r=cuviper Update llvm-project to include PR 73 rust-lang/llvm-project#73 r? @cuviper
vext01
pushed a commit
to vext01/llvm-project
that referenced
this pull request
Jul 11, 2023
73: Simplify the control point. r=ltratt a=ptersilie Co-authored-by: Lukas Diekmann <lukas.diekmann@gmail.com>
nikic
pushed a commit
to nikic/llvm-project
that referenced
this pull request
Nov 2, 2023
…vg (llvm#70914) This removes explicit invalidation of vg and svg that was done in `GDBRemoteRegisterContext::AArch64Reconfigure`. This was in fact covering up a bug elsehwere. Register information says that a write to vg also invalidates svg (it does not unless you are in streaming mode, but we decided to keep it simple and say it always does). This invalidation was not being applied until *after* AArch64Reconfigure was called. This meant that without those manual invalidates this happened: * vg is written * svg is not invalidated * Reconfigure uses the written vg value * Reconfigure uses the *old* svg value I have moved the AArch64Reconfigure call to after we've processed the invalidations caused by the register write, so we no longer need the manual invalidates in AArch64Reconfigure. In addition I have changed the order in which expedited registers as parsed. These registers come with a stop notification and include, amongst others, vg and svg. So now we: * Parse them and update register values (including vg and svg) * AArch64Reconfigure, which uses those values, and invalidates every register, because offsets may have changed. * Parse the expedited registers again, knowing that none of the values will have changed due to the scaling. This means we use the expedited registers during the reconfigure, but the invalidate does not mean we throw all of them away. The cost is we parse them twice client side, but this is cheap compared to a network packet, and is limited to AArch64 targets only. On a system with SVE and SME, these are the packets sent for a step: ``` (lldb) b-remote.async> < 803> read packet: $T05thread:p1f80.1f80;name:main.o;threads:1f80;thread-pcs:000000000040056c<...>a1:0800000000000000;d9:0400000000000000;reason:trace;#fc intern-state < 21> send packet: $xfffffffff200,200#5e intern-state < 516> read packet: $e4f2ffffffff000000<...>rust-lang#71 intern-state < 15> send packet: $Z0,400568,4#4d intern-state < 6> read packet: $OK#9a dbg.evt-handler < 16> send packet: $jThreadsInfo#c1 dbg.evt-handler < 224> read packet: $[{"name":"main.o","reason":"trace","registers":{"161":"0800000000000000",<...>}],"signal":5,"tid":8064}]]rust-lang#73 ``` You can see there are no extra register reads which means we're using the expedited registers. For a write to vg: ``` (lldb) register write vg 4 lldb < 37> send packet: $Pa1=0400000000000000;thread:1f80;#4a lldb < 6> read packet: $OK#9a lldb < 20> send packet: $pa1;thread:1f80;rust-lang#29 lldb < 20> read packet: $0400000000000000#04 lldb < 20> send packet: $pd9;thread:1f80;rust-lang#34 lldb < 20> read packet: $0400000000000000#04 ``` There is the initial P write, and lldb correctly assumes that SVG is invalidated by this also so we read back the new vg and svg values afterwards.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…d write_string/length_of_string
The
__attribute__((destructor(100)))diagnostic does not have awarning option in GCC 8 (before r264853) and thus cannot be suppressed.
--
ported from llvm/llvm-project fix:
llvm@1cfde14
https://bugs.llvm.org/show_bug.cgi?id=47399
(Fixes problem behind rust-lang/rust#76224)