This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On Mon, Jan 13, 2003 at 03:44:18PM -0600, Wolfgang Bangerth wrote: > > On Mon, 13 Jan 2003, Robert Schiele wrote: > > > 1. This problem does not occur with gcc 3.2 or earlier. > > > > 2. This problem does also occur with Andreas' gcc package shipped with > > SuSE 8.1 distribution, which is something between 3.2 and 3.2.1 > > plus some additional changes. > > > > Or has someone else archived builds? > > I have mainline snapshots from the last two years for about every two > weeks, and none of them shows the behavior you see. You still didn't answer my question, which binutils you use. Might be this information is of some use to understand the problem. > Now this is RedHat, so I checked my other system with SuSE, and I cannot Which releases of RedHat and SuSE? I assume the technical differences between some releases are bigger than the general differences between RedHat, SuSE or most of the other distributions. > see the problem there either, not with the 3.2 release nor with a 3.2.2pre > CVS from 4 weeks ago. So I can see only two possibilities: > - it's a SuSE specific patch No, this is not the case, as this also happens with the official 3.2.1, the current 3.2, 3.3 and HEAD branches from cvs _without_ any special patch. I just mentioned the SuSE release as an additional information that should make debugging easier for the one that has an idea what could be the problem here, my intention was not to confuse people with that information. > - it's something with your particular system. I don't think so. I have checked that on more than ten systems including one fresh out-of-the-box SuSE 8.1 installation. On all those systems the same thing happens: 3.2 works correctly, but 3.2.1 and any of the 3.2, 3.3 and HEAD branches do _not_ work correctly. > What do we do with this report? I hope you do not ignore it. My colleague and I have invested some time to track this down to such a simple test case. (The real world test case were megabytes of code.) Might be, that this is an issue with a SuSE 8.1 system. So could someone that has such a system try to reproduce the problem? (Andreas?) The best thing might be if someone that has multiple systems including a SuSE 8.1 could test on which systems he can reproduce the problem and on which not. Robert -- Robert Schiele Tel.: +49-621-181-2517 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
Attachment:
msg00858/pgp00000.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |