Import crt{begin,end}.S from NetBSD
NetBSD has replacements for GCC's crt{begin,end}.S:
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/csu/arch/?only_with_tag=MAIN
This would complement compiler-rt and libstdc++. We intend to import it
in downstream Gentoo FreeBSD.
Could this be imported into FreeBSD-CURRENT?
___
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: Import crt{begin,end}.S from NetBSD
On Thu, 14 Jun 2012 14:54:28 -0400
Richard Yao r...@gentoo.org wrote:
NetBSD has replacements for GCC's crt{begin,end}.S:
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/csu/arch/?only_with_tag=MAIN
This would complement compiler-rt and libstdc++. We intend to import
it in downstream Gentoo FreeBSD.
Could this be imported into FreeBSD-CURRENT?
Apart from licensing, what others reasons are there to do that?
--
Alexander Kabaev
signature.asc
Description: PGP signature
Re: Import crt{begin,end}.S from NetBSD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/12 20:51, Alexander Kabaev wrote:
On Thu, 14 Jun 2012 14:54:28 -0400
Richard Yao r...@gentoo.org wrote:
NetBSD has replacements for GCC's crt{begin,end}.S:
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/csu/arch/?only_with_tag=MAIN
This would complement compiler-rt and libstdc++. We intend to import
it in downstream Gentoo FreeBSD.
Could this be imported into FreeBSD-CURRENT?
Apart from licensing, what others reasons are there to do that?
These components should not be tied to a specific compiler. If GCC is
going to be deprecated, then they should be replaced.
Anyway, having this tied to GCC has caused headaches for Clang
integration in Gentoo. In particular, we let the user pick the toolchain
that he uses, so we cannot place GCC's crt{begin,end}.o in the same
location that FreeBSD uses. This makes it difficult for Clang to find
the correct crt{begin,end}.o. We will likely import the NetBSD
crt{begin,end}.S code to rectify this, but it would be preferable to do
this in upstreamFreeBSD.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP2pcyAAoJECDuEZm+6ExkVTgP/0fjD1+pvrwKypxIg9KoqJ0+
iwKcKVir8Hwi+lADb2xG1rmDXK/KuFp838Fxr02HTECsWKnH477GNb5WNiDT52Uc
jHfs9g8lY7W4BRNjnbVj0RxgZx8xhLFnrOUBrvkTd84Y5Mi+Y0qXx19+2L+NFVGd
ZHY6ndeggAsyhAo0kaakMLqnAPDqjHhgk7SUJPeH/Zy7KtrO8MFeEwNUVzjXYytW
YXmayxqyDjtN0UdYC7vHnes5dA6aiWDN4/LZTzybRz0GGaKkOXPPoN5QBFUen91j
YHwiCh9NxHOXdEuYLYk1PVu29T6lUE+4U+2k57wRsODEnhgwDyh5184wYfs3gp2k
ttsgBun4aH0AHNdUK6G0XLx/dR7hAPxommmRYVclr/7EpCYhHRDKGvGXUvK8XC79
+ON55vfGCho3kqevjGsQZR1f5hXbKKaKu8JqGQT3LaGz1eSs8jLRDilYA7nTKstY
rx83HU0YQa9c+NdZBYnHXgwjJXJLxIL6rr8E7NQE/co99iNKnHgyar9B6RwbDLMZ
iHX5PUOXikb7OOaXGTNCQas59eO6tHnNrWbmknm59w8fkOjXeiKEliT3Xk8qlLZx
l29JmAPMYzuNNoF0RJJ9QvUUJ9Q8CVScrzJVw4PuVdzJMSrKmG9/ggh2yDw161Lp
DJ8ETPIuVOCGdH2G2mqs
=51Ky
-END PGP SIGNATURE-
___
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: Import crt{begin,end}.S from NetBSD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 14 Jun 2012 22:00:18 -0400
Richard Yao r...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/12 20:51, Alexander Kabaev wrote:
On Thu, 14 Jun 2012 14:54:28 -0400
Richard Yao r...@gentoo.org wrote:
NetBSD has replacements for GCC's crt{begin,end}.S:
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/csu/arch/?only_with_tag=MAIN
This would complement compiler-rt and libstdc++. We intend to
import it in downstream Gentoo FreeBSD.
Could this be imported into FreeBSD-CURRENT?
Apart from licensing, what others reasons are there to do that?
These components should not be tied to a specific compiler. If GCC is
going to be deprecated, then they should be replaced.
Anyway, having this tied to GCC has caused headaches for Clang
integration in Gentoo. In particular, we let the user pick the
toolchain that he uses, so we cannot place GCC's crt{begin,end}.o in
the same location that FreeBSD uses. This makes it difficult for
Clang to find the correct crt{begin,end}.o. We will likely import the
NetBSD crt{begin,end}.S code to rectify this, but it would be
preferable to do this in upstreamFreeBSD.
Assuming NetBSD version is a direct plugin for crtbegin/end provided
by GCC, I see no reason why we cannot do that. Are you are willing to do
the work and submit the patch, or would like to wait for someone on
our side?
- --
Alexander Kabaev
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (FreeBSD)
iD8DBQFP2pzlQ6z1jMm+XZYRAj9DAKDiYhGiRDL9Ow8/fkcBW+EOX1DrJwCfdJH7
bL9t1FXvMhua6bu2Sv5BwGE=
=DbLg
-END PGP SIGNATURE-
___
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: Import crt{begin,end}.S from NetBSD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/12 22:24, Alexander Kabaev wrote:
On Thu, 14 Jun 2012 22:00:18 -0400 Richard Yao r...@gentoo.org
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 06/14/12 20:51, Alexander Kabaev wrote:
On Thu, 14 Jun 2012 14:54:28 -0400 Richard Yao
r...@gentoo.org wrote:
NetBSD has replacements for GCC's crt{begin,end}.S:
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/csu/arch/?only_with_tag=MAIN
This would complement compiler-rt and libstdc++. We intend to
import it in downstream Gentoo FreeBSD.
Could this be imported into FreeBSD-CURRENT?
Apart from licensing, what others reasons are there to do
that?
These components should not be tied to a specific compiler. If
GCC is going to be deprecated, then they should be replaced.
Anyway, having this tied to GCC has caused headaches for Clang
integration in Gentoo. In particular, we let the user pick the
toolchain that he uses, so we cannot place GCC's crt{begin,end}.o
in the same location that FreeBSD uses. This makes it difficult
for Clang to find the correct crt{begin,end}.o. We will likely
import the NetBSD crt{begin,end}.S code to rectify this, but it
would be preferable to do this in upstreamFreeBSD.
Assuming NetBSD version is a direct plugin for crtbegin/end
provided by GCC, I see no reason why we cannot do that. Are you are
willing to do the work and submit the patch, or would like to wait
for someone on our side?
Gentoo FreeBSD is currently based on FreeBSD 9-RELEASE. I plan to do
the work to import this downstream within the week, but I am not
running CURRENT. It might be necessary to iterate on the patches
before they can be merged. When I have them, should I file a PR or
post them to the list?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP2qB8AAoJECDuEZm+6Exk9YIP/ih8FwyH48zp1GH4vtlF3NAq
kxqCefhDvgys+np6eYO65W7Gy55NGlwXuRlI8V5sVPea8pgFAXPceGureKrdJCda
HpTdSi/KTAg0Is9PO6Ev4AoLYhEslCbMbQCOAWhRymZIn2MuuEQMjWw8aRWayebJ
VVAIBLzUGrWlHxwfgkaxvO5V4obbetVFewJH+3X9kUDDawXZAYuTl+Llo4GW7lLn
z8/rOciUDqDKy1vFr7R/9998ruJpRG5hAfeA/ovZTUYkO0bmAOpMWrjA9z/rzBEq
2kKAyeQLYfcCtChWvtl3y3WwhBp7uJfbKhiNZlbg8iVZ4YVVJ4xxFUCsz+7CvAwt
BTJ3/Lt1xdrxvMTE/N8b/AwRW/sGgeEqdukPHFhhIbkYRHvvhU7LC7fXC3UxfhP4
J+KHQS1e2jjqqJUnFKa1g5AE6heB2ZlfCNIJH3pZXYGAfz9ff4000az+u9klYSOY
58mL3IR9X0BZboyG263P5cVsyYuT3BEhpEIhUzcvfJvS+vD8lBSYhkub2tgx27Hu
+ov0zvhefZfOpnIRv8K4/KTuEd2scVx4hwOOcnr79PZhPfuyEqqybqrgUJeHH7in
cviufLF0YpMwAutiE5g5ySKPlomKjRR3jRhJO9KyQ0giViT5Ppt/aq4UHb6WJDtf
KVWinFLrnibIKUWJczXZ
=brrQ
-END PGP SIGNATURE-
___
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: Import crt{begin,end}.S from NetBSD
On Thu, Jun 14, 2012 at 7:39 PM, Richard Yao r...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/12 22:24, Alexander Kabaev wrote:
On Thu, 14 Jun 2012 22:00:18 -0400 Richard Yao r...@gentoo.org
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 06/14/12 20:51, Alexander Kabaev wrote:
On Thu, 14 Jun 2012 14:54:28 -0400 Richard Yao
r...@gentoo.org wrote:
NetBSD has replacements for GCC's crt{begin,end}.S:
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/csu/arch/?only_with_tag=MAIN
This would complement compiler-rt and libstdc++. We intend to
import it in downstream Gentoo FreeBSD.
Could this be imported into FreeBSD-CURRENT?
Apart from licensing, what others reasons are there to do
that?
These components should not be tied to a specific compiler. If
GCC is going to be deprecated, then they should be replaced.
Anyway, having this tied to GCC has caused headaches for Clang
integration in Gentoo. In particular, we let the user pick the
toolchain that he uses, so we cannot place GCC's crt{begin,end}.o
in the same location that FreeBSD uses. This makes it difficult
for Clang to find the correct crt{begin,end}.o. We will likely
import the NetBSD crt{begin,end}.S code to rectify this, but it
would be preferable to do this in upstreamFreeBSD.
Assuming NetBSD version is a direct plugin for crtbegin/end
provided by GCC, I see no reason why we cannot do that. Are you are
willing to do the work and submit the patch, or would like to wait
for someone on our side?
Gentoo FreeBSD is currently based on FreeBSD 9-RELEASE. I plan to do
the work to import this downstream within the week, but I am not
running CURRENT. It might be necessary to iterate on the patches
before they can be merged. When I have them, should I file a PR or
post them to the list?
File a PR, post a link to the PR on a list / to devs generally is
the best way to go.
Thanks!
-Garrett
___
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
