<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/tests/codegen/method-declaration.rs, branch 1.76.0</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.76.0</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.76.0'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2023-08-12T13:27:46+00:00</updated>
<entry>
<title>Add test for method debuginfo declaration.</title>
<updated>2023-08-12T13:27:46+00:00</updated>
<author>
<name>DianQK</name>
<email>dianqk@dianqk.net</email>
</author>
<published>2023-08-12T13:25:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=6f5b4e358145066dfe76251e89eb40c531c4bb51'/>
<id>urn:sha1:6f5b4e358145066dfe76251e89eb40c531c4bb51</id>
<content type='text'>
We've investigated one reason why debugging information often goes wrong at https://reviews.llvm.org/D152095.
&gt; LLVM can't handle IR where subprogram definitions are nested within DICompositeType when doing LTO builds,
&gt; because there's no good way to cross the CU boundary to insert a nested DISubprogram definition in one CU into a type defined in another CU.
</content>
</entry>
</feed>
