[Bug gas/10193] gas produces different .o files with the same input .s file and cmd line arguments on enfs

2009-05-25 Thread chenyang dot cq at gmail dot com
--- Additional Comments From chenyang dot cq at gmail dot com 2009-05-25 08:22 --- You have a filesystem problem. gas isn't writing these bytes, and a sane filesystem would set them to zeros. So, not a gas bug. Why not explicitly set them to zeros so that gas can work well with those

[Bug gas/10193] gas produces different .o files with the same input .s file and cmd line arguments on enfs

2009-05-25 Thread amodra at bigpond dot net dot au
--- Additional Comments From amodra at bigpond dot net dot au 2009-05-26 00:19 --- Because that would be more work in BFD if we wanted to catch all possible cases of padding, slowing down all file writes. You could of course patch your own binutils sources. The place that skipped

[Bug gas/10193] gas produces different .o files with the same input .s file and cmd line arguments on enfs

2009-05-23 Thread chenyang dot cq at gmail dot com
--- Additional Comments From chenyang dot cq at gmail dot com 2009-05-23 13:55 --- Created an attachment (id=3960) -- (http://sourceware.org/bugzilla/attachment.cgi?id=3960action=view) testtree.s obj1.o obj2.o the assembler file and two different result object files. --