Re: [kbuild-devel] Mucking with assembly files
On Tue, Jul 10, 2007 at 10:19:14AM -0700, H. Peter Anvin wrote: I seem to always be the one with the kbuild corner cases... As part of my x86 setup rewrite, there has been some concern that using asm(.code16gcc); isn't as safe as it should be (because of gcc reordering), and making it safe apparently means disabling optimizations that adds at least 5% to the code size. Not really a huge deal, but undesirable in the long run. The alternative is to compile to a .s file and then inject .code16gcc to the top of the .s file before assembling it into a .o file. This means overriding some of kbuild's implicit rules, and I'm not sure how to do that cleanly. Is this still relevant considering you adopted the -funit-at-a-time proposal? Sam - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] Mucking with assembly files
On Tue, Jul 10, 2007 at 09:46:25PM +0200, Oleg Verych wrote: On Tue, Jul 10, 2007 at 10:19:14AM -0700, H. Peter Anvin wrote: I seem to always be the one with the kbuild corner cases... As part of my x86 setup rewrite, there has been some concern that using asm(.code16gcc); isn't as safe as it should be (because of gcc reordering), and making it safe apparently means disabling optimizations that adds at least 5% to the code size. Not really a huge deal, but undesirable in the long run. The alternative is to compile to a .s file and then inject .code16gcc to the top of the .s file before assembling it into a .o file. This means overriding some of kbuild's implicit rules, and I'm not sure how to do that cleanly. As part of my kbuild/kconfig pre-rewrite info collecting... whatever :) I did asm-offsets build rewrite RFC four week ago: http://mid.gmane.org/[EMAIL PROTECTED] You may be interested in it. But Sam is busy, nothing happend since then. Just returned from a nice 2 week vacation with no Internet access and no computer turned on (not counting the GPS). And still lacking behind on other stuff too. Sam - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] Mucking with assembly files
On Tue, Jul 10, 2007 at 10:19:14AM -0700, H. Peter Anvin wrote: I seem to always be the one with the kbuild corner cases... As part of my x86 setup rewrite, there has been some concern that using asm(.code16gcc); isn't as safe as it should be (because of gcc reordering), and making it safe apparently means disabling optimizations that adds at least 5% to the code size. Not really a huge deal, but undesirable in the long run. The alternative is to compile to a .s file and then inject .code16gcc to the top of the .s file before assembling it into a .o file. This means overriding some of kbuild's implicit rules, and I'm not sure how to do that cleanly. As part of my kbuild/kconfig pre-rewrite info collecting... whatever :) I did asm-offsets build rewrite RFC four week ago: http://mid.gmane.org/[EMAIL PROTECTED] You may be interested in it. But Sam is busy, nothing happend since then. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel