search for: 1102223

Signed-off-by: Karol Herbst <nouveau at karolherbst.de> --- drm/nouveau/nvkm/subdev/clk/base.c | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/subdev/clk/base.c b/drm/nouveau/nvkm/subdev/clk/base.c index 889cce2..4928668 100644 --- a/drm/nouveau/nvkm/subdev/clk/base.c +++ b/drm/nouveau/nvkm/subdev/clk/base.c @@ -24,6 +24,7 @@ #include

...#39;t handle -1 well at all (essentially unusable) - gdb's line table parsing ends up with different handling when breaking on gc'd functions (minor functionality issue) - chromium/firefox have some tools that were broken: https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 I think there's enough risk in this work (even given the small number of bugs found so far), given there's a pretty wide array of debug info consumers out there, that we should change lld's default to match the long-lived bfd strategy. This would address my original motivation for...

...es of DWARF I'd guess. (what about stack unwinding using >debug_frame? that'd worry me a bit if anyone got /that/ wrong because >of this change) > >> > - chromium/firefox have some tools that were broken: >> > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 >> >> This is potentially related to other .debug_* (not .debug_line) >> I hope Chromium developers can chime in here:) The breakage was >> unfortunate but I don't know how we could have avoided that. IMHO this >> is no different from "clang started to emit...

...because > >>> > > > >of this change) > >>> > > > > > >>> > > > >> > - chromium/firefox have some tools that were broken: > >>> > > > >> > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5<https://urldefense.com/v3/__https:/bugs.chromium.org/p/chromium/issues/detail?id=1102223*c5__;Iw!!JmoZiZGBv3RvKRSx!ofVK1otXjQ1pPSV3TC8HS9Gwe9JwuC91OgFyvfCtZ57p55u8aHljgBgPTWa5dfJfdQ$> > >>> > > > >> > >>> > > > >> This is potentially re...

...nding using > > >debug_frame? that'd worry me a bit if anyone got /that/ wrong because > > >of this change) > > > > > >> > - chromium/firefox have some tools that were broken: > > >> > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 > > >> > > >> This is potentially related to other .debug_* (not .debug_line) > > >> I hope Chromium developers can chime in here:) The breakage was > > >> unfortunate but I don't know how we could have avoided that. IMHO this > > >&gt...

...s. (what about stack unwinding using > >debug_frame? that'd worry me a bit if anyone got /that/ wrong because > >of this change) > > > >> > - chromium/firefox have some tools that were broken: > >> > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 > >> > >> This is potentially related to other .debug_* (not .debug_line) > >> I hope Chromium developers can chime in here:) The breakage was > >> unfortunate but I don't know how we could have avoided that. IMHO this > >> is no different from &q...

...;> > > > >of this change) > > >>> > > > > > > >>> > > > >> > - chromium/firefox have some tools that were broken: > > >>> > > > >> > > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 > > >>> > > > >> > > >>> > > > >> This is potentially related to other .debug_* (not > .debug_line) > > >>> > > > >> I hope Chromium developers can chime in here:) The breakage > was > > >&gt...

...worry me a bit if anyone got /that/ wrong > because > > > > >of this change) > > > > > > > > > >> > - chromium/firefox have some tools that were broken: > > > > >> > > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 > > > > >> > > > > >> This is potentially related to other .debug_* (not .debug_line) > > > > >> I hope Chromium developers can chime in here:) The breakage was > > > > >> unfortunate but I don't know how we could have a...

...ne got /that/ wrong because >>> > > > >of this change) >>> > > > > >>> > > > >> > - chromium/firefox have some tools that were broken: >>> > > > >> > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 >>> > > > >> >>> > > > >> This is potentially related to other .debug_* (not .debug_line) >>> > > > >> I hope Chromium developers can chime in here:) The breakage was >>> > > > >> unfortunate but I do...

...gt; > > >of this change) >> > >>> > > > > >> > >>> > > > >> > - chromium/firefox have some tools that were broken: >> > >>> > > > >> > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 >> > >>> > > > >> >> > >>> > > > >> This is potentially related to other .debug_* (not .debug_line) >> > >>> > > > >> I hope Chromium developers can chime in here:) The breakage was >> > &...

...t;> >> > >>> > > > > >> >> > >>> > > > >> > - chromium/firefox have some tools that were broken: >> >> > >>> > > > >> > >> https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 >> >> > >>> > > > >> >> >> > >>> > > > >> This is potentially related to other .debug_* (not >> .debug_line) >> >> > >>> > > > >> I hope Chromium developers can chime in her...

...t;> > > > > >> >> >> > >>> > > > >> > - chromium/firefox have some tools that were broken: >> >> >> > >>> > > > >> > >> >> https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 >> >> >> > >>> > > > >> >> >> >> > >>> > > > >> This is potentially related to other .debug_* (not >> >> .debug_line) >> >> >> > >>> > > > >> I hope...

...; > >> >> >> > >>> > > > >> > - chromium/firefox have some tools that were broken: > > >> >> >> > >>> > > > >> > > > >> >> https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 > > >> >> >> > >>> > > > >> > > >> >> >> > >>> > > > >> This is potentially related to other .debug_* (not > > >> >> .debug_line) > > >> >> >> > >...

...gt; > >>> > > > >> > - chromium/firefox have some tools that > were broken: > > > > >> >> >> > >>> > > > >> > > > > > >> >> > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 > > > > >> >> >> > >>> > > > >> > > > > >> >> >> > >>> > > > >> This is potentially related to other > .debug_* (not > > > > >> >> .debug_line) > > &...

...gt; > > > >> > - chromium/firefox have some tools that > were broken: > >> > > > >> >> >> > >>> > > > >> > > >> > > > >> >> > https://bugs.chromium.org/p/chromium/issues/detail?id=1102223#c5 > >> > > > >> >> >> > >>> > > > >> > >> > > > >> >> >> > >>> > > > >> This is potentially related to other > .debug_* (not > >> > > > >> >&g...