From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Buck To: hjl@lucon.org (H.J. Lu) Cc: jbuck@Synopsys.COM, sb@metis.no, egcs@egcs.cygnus.com Subject: Re: egcs and linux Date: Tue, 16 Feb 1999 10:06:00 -0000 Message-id: <199902161805.KAA18983@atrus.synopsys.com> In-reply-to: < m10CZUe-00038sC@ocean.lucon.org >; from "H.J. Lu" at Feb 15, 99 5:40 pm References: X-SW-Source: 1999-02/msg00726.html HJ writes: > Please remember egcs is used as a native compiler on Linux. > Many Linux testcases are quite complicated. As you have noted > that those bugs only show up in specific circumstances. A testcase > may mean > > 1. A Linux machine with specific packages installed. > 2. A Makefile and several source files. > > How can such a testcase be included in the egcs testsuite? #1 can't be included; #2, in theory, could be. Since the real problem is often glibc/libstdc++ interaction, or issues with dynamic linking, I wouldn't be surprised if some of these failures show up also on the Hurd (e.g. in the Debian/HURD system people are putting together) or even with dynamic linking on other ELF systems. This means you wouldn't want to include #1 even if you wanted to, you'd just describe cases where you expect failures. We can't currently handle Makefiles in the test suite, but perhaps we can just have a separate set of tests for these problems, maybe in /pub/egcs/contrib or something, which would be invoked by simply typing "make" (which would then build a tree). There's been work on multiple-file tests, but I haven't looked at it. I would then support you in saying that egcs 1.1.2 must run those tests correctly (you could describe the problematic systems or how to duplicate failures). From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Buck To: hjl@lucon.org (H.J. Lu) Cc: jbuck@Synopsys.COM, sb@metis.no, egcs@egcs.cygnus.com Subject: Re: egcs and linux Date: Sun, 28 Feb 1999 22:53:00 -0000 Message-ID: <199902161805.KAA18983@atrus.synopsys.com> References: X-SW-Source: 1999-02n/msg00723.html Message-ID: <19990228225300.hMpDY9PbYml4natKT937NruPHIPSVGuGPOs6QCcMUpo@z> HJ writes: > Please remember egcs is used as a native compiler on Linux. > Many Linux testcases are quite complicated. As you have noted > that those bugs only show up in specific circumstances. A testcase > may mean > > 1. A Linux machine with specific packages installed. > 2. A Makefile and several source files. > > How can such a testcase be included in the egcs testsuite? #1 can't be included; #2, in theory, could be. Since the real problem is often glibc/libstdc++ interaction, or issues with dynamic linking, I wouldn't be surprised if some of these failures show up also on the Hurd (e.g. in the Debian/HURD system people are putting together) or even with dynamic linking on other ELF systems. This means you wouldn't want to include #1 even if you wanted to, you'd just describe cases where you expect failures. We can't currently handle Makefiles in the test suite, but perhaps we can just have a separate set of tests for these problems, maybe in /pub/egcs/contrib or something, which would be invoked by simply typing "make" (which would then build a tree). There's been work on multiple-file tests, but I haven't looked at it. I would then support you in saying that egcs 1.1.2 must run those tests correctly (you could describe the problematic systems or how to duplicate failures).