Re: Clang '-g' unused warnings in FreeBSD (linking)
Thanks, both replies were very informative! Regarding > one could argue that passing '-g' to the link stage is nonsensical, > since ld cannot add debug information, it can only remove it (via the '-s' > flag). Is precisely why I was asking If this was conscious decision on FreeBSD part. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Clang-g-unused-warnings-in-FreeBSD-linking-tp5727055p5727113.html Sent from the freebsd-hackers mailing list archive at Nabble.com. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Clang '-g' unused warnings in FreeBSD (linking)
On Sun, Jul 15, 2012 at 07:32:35PM +0200, Dimitry Andric wrote: > On 2012-07-15 15:39, Jakub Lach wrote: > > While this is old "bug" upstream: > > > > http://llvm.org/bugs/show_bug.cgi?id=8611 > > > > http://llvm.org/bugs/show_bug.cgi?id=8630 > > > > Here, > > > > (FreeBSD clang version 3.1 (branches/release_31 156863) 20120523 > > Target: x86_64-unknown-freebsd9.0) > > > > Passing -g during linking (which lot's of projects do by > > including CFLAGS in linking) I still get > > > > "clang: warning: argument unused during compilation: '-g'" > ... > On 2012-07-15 16:04, Jakub Lach wrote: > > Maybe I should include a question too, so I have better chance > > of getting answer :) > > > > Is this intended behaviour? > > This is a bit typical issue for clang, which originates in the way it > parses command line arguments: different parts of the compiler stages > 'claim' arguments, and any that are left at the end are reported as > unused. > > Regarding the LLVM PRs you mentioned, one could argue that passing '-g' > to the link stage is nonsensical, since ld cannot add debug information, > it can only remove it (via the '-s' flag). But since it is apparently > common to do this, it may be a bit too annoying to complain about it. > > In any case, upstream fixed it for Linux, but not for any other > operating system. I will make a similar fix for FreeBSD, and send it > upstream too. Note that historical ld(1) did emited debugging information into resulting binary only if -g was specified, so the linker flag is not always 'meaningless'. I suspect that Solaris ld still behaves this way. pgpRaO53aujil.pgp Description: PGP signature
Re: Clang '-g' unused warnings in FreeBSD (linking)
On 2012-07-15 15:39, Jakub Lach wrote: > While this is old "bug" upstream: > > http://llvm.org/bugs/show_bug.cgi?id=8611 > > http://llvm.org/bugs/show_bug.cgi?id=8630 > > Here, > > (FreeBSD clang version 3.1 (branches/release_31 156863) 20120523 > Target: x86_64-unknown-freebsd9.0) > > Passing -g during linking (which lot's of projects do by > including CFLAGS in linking) I still get > > "clang: warning: argument unused during compilation: '-g'" ... On 2012-07-15 16:04, Jakub Lach wrote: > Maybe I should include a question too, so I have better chance > of getting answer :) > > Is this intended behaviour? This is a bit typical issue for clang, which originates in the way it parses command line arguments: different parts of the compiler stages 'claim' arguments, and any that are left at the end are reported as unused. Regarding the LLVM PRs you mentioned, one could argue that passing '-g' to the link stage is nonsensical, since ld cannot add debug information, it can only remove it (via the '-s' flag). But since it is apparently common to do this, it may be a bit too annoying to complain about it. In any case, upstream fixed it for Linux, but not for any other operating system. I will make a similar fix for FreeBSD, and send it upstream too. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Clang '-g' unused warnings in FreeBSD (linking)
Maybe I should include a question too, so I have better chance of getting answer :) Is this intended behaviour? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Clang-g-unused-warnings-in-FreeBSD-linking-tp5727055p5727066.html Sent from the freebsd-hackers mailing list archive at Nabble.com. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Clang '-g' unused warnings in FreeBSD (linking)
Hello. While this is old "bug" upstream: http://llvm.org/bugs/show_bug.cgi?id=8611 http://llvm.org/bugs/show_bug.cgi?id=8630 Here, (FreeBSD clang version 3.1 (branches/release_31 156863) 20120523 Target: x86_64-unknown-freebsd9.0) Passing -g during linking (which lot's of projects do by including CFLAGS in linking) I still get "clang: warning: argument unused during compilation: '-g'" -- View this message in context: http://freebsd.1045724.n5.nabble.com/Clang-g-unused-warnings-in-FreeBSD-linking-tp5727055.html Sent from the freebsd-hackers mailing list archive at Nabble.com. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD 8.3
being a lot like using a poor wireless mouse. My thanks to everyone who took time to help me. by the way anyone know WHY BIOS is over control of that CPU feature? It is quite scary to know that my FreeBSD system isn't really under FreeBSD control. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD 8.3
On 07/15/2012 02:39, Mike Meyer wrote: > On Sat, 14 Jul 2012 13:29:59 -0700 > Doug Barton wrote: > >> For the OP, make sure you have the latest BIOS. I had a similar problem >> with vt-x and it was solved by a later BIOS upgrade. > > And *that* solved the problem. The performance is much better, now > being a lot like using a poor wireless mouse. > > My thanks to everyone who took time to help me. I'm glad to help, and more glad that it was that simple of a solution. :) Doug -- Change is hard. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD 8.3
On Sat, 14 Jul 2012 13:29:59 -0700 Doug Barton wrote: > For the OP, make sure you have the latest BIOS. I had a similar problem > with vt-x and it was solved by a later BIOS upgrade. And *that* solved the problem. The performance is much better, now being a lot like using a poor wireless mouse. My thanks to everyone who took time to help me. http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
