Re: [PATCH] Fixed tests build on EDG-based compilers

[Илья Курдюков]

The EDG frontend is used by MCST, which designs Elbrus 2000 processors, 
for their compiler named LCC. Which generates the fastest code at the 
moment. There is a Clang backend, but its quality is low (bugs, poor 
performance).

This LCC runs in GNUC compatibility mode, so it has a __GNUC__ macro and 
is mostly compatible with GCC. By the way, Clang also defines the 
__GNUC__ macro.

I have filed a lot of bugs (most are about C++ issues), but I'm doing 
this on MCST bugzilla and they are negotiating with EDG. I have no 
contacts with EDG.

Most of these bugs are also reproduced in ICC (Intel Compiler), which 
also has the __EDG__ and __GNUC__ macros, as you can check in the 
Compiler Explorer.


On 06.12.2021 14:41, Paul Eggert wrote:
> On 12/5/21 15:41, Bruno Haible wrote:
> >    - Why does a compiler define __GNUC__ or __clang__ when it does not
> >      behave like GCC or clang?
> >    - Why are people at altlinux.org attempting to support a proprietary
> >      compiler?
>
> Both good questions, especially since this issue (whatever it is: 
> Ilya's email didn't say) is surely due to a bug in the EDG compiler. 
> What exactly are the symptoms of the EDG compiler bug? Did Ilya file a 
> bug report with EDG about this? What did EDG say? That sort of thing.