This is the mail archive of the gcc@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]

Re: [llvm-dev] GCC 5 and -Wstrict-aliasing in JSON.h

From: Leslie Zhai <zhaixiang at loongson dot cn>
To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
Cc: kim dot grasman at gmail dot com, rguenth at gcc dot gnu dot org, sam dot mccall at gmail dot com, llvm-dev at lists dot llvm dot org, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Thu, 9 Aug 2018 19:04:35 +0800
Subject: Re: [llvm-dev] GCC 5 and -Wstrict-aliasing in JSON.h
References: <CANt7B+dnBTK75FOqO+TcgvdcDZm9zv0WAawxx+XEHNMuMkdHuA@mail.gmail.com> <55c64df9-54ca-9cd4-670e-2439a7fc9095@loongson.cn> <CAH6eHdRoh9a0fhnNJMSL2sD894672x5xK-K-dscaAMeq=1xyzQ@mail.gmail.com>

Hi Jonathan,

Thanks for your response!

So workaround for Kim's issue is bootstrap old version LLVM with GCC 4/5to build old clang, then bootstrap latest LLVM with old clang.



在 2018年08月09日 17:16, Jonathan Wakely 写道:

On Thu, 9 Aug 2018 at 03:09, Leslie Zhai wrote:

Could you test to compile LLVM with GCC old versions 4/5/6? Does it need
to backport your patch to GCC old version?

GCC versions before 6.4 are not supported, so no backports will happen
to 4.x or 5 releases and I doubt anybody's going to routinely test
anything with them. If there's a bug in GCC 4.9.3 that you can't work
around then you should upgrade to a supported release (or use a
distribution that provides support for older releases).


--
Regards,
Leslie Zhai

Follow-Ups:
- Re: [llvm-dev] GCC 5 and -Wstrict-aliasing in JSON.h
  - From: Jonathan Wakely

References:
- Re: [llvm-dev] GCC 5 and -Wstrict-aliasing in JSON.h
  - From: Leslie Zhai
- Re: [llvm-dev] GCC 5 and -Wstrict-aliasing in JSON.h
  - From: Jonathan Wakely

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]