[Bug middle-end/44308] ranlib: file: libbackend

2010-05-31 Thread jay dot krell at cornell dot edu
--- Comment #4 from jay dot krell at cornell dot edu 2010-05-31 12:14 --- Here is the fix for insn-peep.o (against 4.3, granted): diff -u -r1.5 genpeep.c --- gcc/gcc/genpeep.c 14 Apr 2008 12:48:21 - 1.5 +++ gcc/gcc/genpeep.c 31 May 2010 12:14:37 - @@ -424,6 +424,7 @@

[Bug middle-end/44308] ranlib: file: libbackend

2010-05-30 Thread jay dot krell at cornell dot edu
--- Comment #3 from jay dot krell at cornell dot edu 2010-05-30 08:55 --- Hm. There are more. Perhaps better to not compile/lib/link files that can be easily predicted to have no symbols? Maybe just ignore it. Maybe get Apple to change ranlib. Maybe they already have. ranlib: file: ../

[Bug middle-end/44308] ranlib: file: libbackend

2010-05-30 Thread jay dot krell at cornell dot edu
--- Comment #2 from jay dot krell at cornell dot edu 2010-05-30 08:06 --- I understand it is "ok". Question is: Do you want to be warning free? At what cost? I think you do, at some finite cost, and I think the change is worthwhile here. This isn't adding symbols at random, it is adding

[Bug middle-end/44308] ranlib: file: libbackend

2010-05-28 Thread steven at gcc dot gnu dot org
--- Comment #1 from steven at gcc dot gnu dot org 2010-05-28 13:06 --- This is OK, those files have only content for certain configurations (with CLOOG, doloop pattern in the backend, etc.). You should look for a way to suppress the warning without adding new symbols at random. -- s