https://sourceware.org/bugzilla/show_bug.cgi?id=23153
--- Comment #10 from Florian Weimer <fweimer at redhat dot com> --- (In reply to Nick Clifton from comment #9) > My assumption is that even if inode 0 is valid for the filesystem it is > extremely unlikely that this value will just happen to be used for an > assembler input file, > and extremely unlucky if this file is then used as the output from the > assembler too. So basically, it is not worth worrying about. Agreed. If this safety check does not kick in because the input and output files are the same and have inode 0, then this is not a huge problem. I just wanted to point out that inode number 0 is *not* special on most systems because that's a common misconception. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
