search for: nouwtable

...gt;        !0 = metadata !{ void ()* @foo, double (i32)* @bar } >        !fno.omit.frame.pointer = !{ !0 } > > And so on. This part I am not so sure about. I fixed a similar problem for unwind tables by adding an attribute. It could be safely done with a metadata with the oposite meaning (nouwtable). The things I am uncomfortable with this part of the proposal are: * Why not use metadata attached directly to the functions? They are the closest thing to an easy to add attribute. * The recent discussion about metadata points out that it is not really safe to add information that only part of...

...()* @foo, double (i32)* @bar } >> !fno.omit.frame.pointer = !{ !0 } >> >> And so on. > > This part I am not so sure about. I fixed a similar problem for unwind > tables by adding an attribute. It could be safely done with a metadata > with the oposite meaning (nouwtable). The things I am uncomfortable > with this part of the proposal are: > > * Why not use metadata attached directly to the functions? They are > the closest thing to an easy to add attribute. > Possible, but the problem with metadata is that it should be possible to remove them from...

Hi, Link-Time Optimization has a problem. We need to preserve some of the flags with which the modules were compiled so that the semantics of the resulting program are correct. For example, a module compiled with `-msoft-float' should use library calls for floating point. And that's only the tip of the proverbial iceberg. Goals ===== My goals for whichever solution we come up with are