Re: [Patch][Demangler] Fix for complex values

3fb593d316abb Mon Sep 17 00:00:00 2001 From: Miguel Saldivar Date: Tue, 29 Oct 2019 09:17:00 -0700 Subject: [PATCH] [Patch] Fix small issue with "demangle-expected" gcc/libiberty/ * testsuite/demangle-expected: Fix test. --- libiberty/ChangeLog | 4 libiberty/testsuit

Re: [Patch][Demangler] Fix for complex values

Updated patch that uses `_Complex` and `_Imaginary` Thanks, Miguel Saldivar >From 742b37c88bea0118046ac359cabe5f250d69ee30 Mon Sep 17 00:00:00 2001 From: Miguel Saldivar Date: Sat, 19 Oct 2019 21:06:07 -0700 Subject: [PATCH] Fix for complex and imaginary values gcc/libiberty/ * cp-demangl

Re: [Patch][Demangler] Fix for complex values

The only reason I wanted `float complex` was for interoperability between the two other demanglers. Although the go demangler does use `_Complex` and `_Imaginary`, so I guess it's sort of split. But I agree, `_Complex` and `_Imaginary` is probably the better option. Thanks, Miguel Saldiva

[Patch][Demangler] Fix for complex values

This is a small fix for Bug 67299, where symbol: `Z1fCf` which would become `f(float complex)` instead of `f(floatcomplex )`. I thought this would be the preferred way of printing, because both `llvm-cxxfilt` and `cpp_filt` both print the the mangled name in this fashion. Thanks, Miguel Saldivar

[PATCH][Demangler] Small fix for complex values

This is a small for Bug 67299, where symbol: `Z1fCf` becomes `f(float complex)` rather than: `f(floatcomplex )`. I thought this would be the preferred way of printing, because both `llvm-cxxfilt` and `cpp_filt` both print the former. Thanks, Miguel Saldivar