On Mon, Oct 26, 2009 at 3:39 PM, Basile STARYNKEVITCH <bas...@starynkevitch.net> wrote: > Richard Guenther wrote: >> >> On Mon, Oct 26, 2009 at 2:59 PM, Ian Lance Taylor <i...@google.com> wrote: >>> >>> Basile STARYNKEVITCH <bas...@starynkevitch.net> writes: >>> >>>> Are you suggesting me to upload to bugzilla the nearly 3000 >>>> preprocessed forms of the files? I could do that, but the *.i files >>>> totalize more than one gigabyte. A bzip2 compressed tar archive of >>>> them is almost 80Mbytes. >>> >>> That is a difficulty, but without a self-contained test case it's >>> pretty hard to fix the bug. You can try reporting the bug with a URL >>> for where to download the sources. Since LTO is fairly new a >>> maintainer may be willing to download them and try it. Otherwise, go >>> ahead and upload that 80M tar ball. gcc.gnu.org will cope. >> >> Please don't. Bi-sect the list of object files by adding -r -nostdlib >> to the link line. This should result in a two or three file testcase. >> Either attach those or reduce them with delta. > > > I am not sure to understand what that means technically. > > The sisegv is gotten by running > > gcc -flto -O2 [A-Z]*.c -rdynamic -ldl -o malice-lto > > where the [A-Z]*.c file glob pattern expand to nearly 3000 files. Exactly > those from http://pagesperso-orange.fr/jacques.pitrat/malice-2009.tar.bz2 > > What command to you suggest me to run? How will I find the faulty files...
See the LTO section in http://gcc.gnu.org/wiki/A_guide_to_testcase_reduction Richard.
