[llvm-dev] [EXTERNAL] Re: bug is APFloat assignment (original) (raw)
Tim Northover via llvm-dev llvm-dev at lists.llvm.org
Tue Oct 16 12:54:15 PDT 2018
- Previous message: [llvm-dev] [EXTERNAL] Re: bug is APFloat assignment
- Next message: [llvm-dev] bug is APFloat assignment
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 16 Oct 2018 at 12:43, Davis, Alan via llvm-dev <llvm-dev at lists.llvm.org> wrote:
I still think it’s a bug, but fairly easy to avoid: either properly construct APF2, or avoid assignment.
It's an issue that's intrinsic to how unions interact with constructors, I think. The standard even mentions it:
"Note: In general, one must use explicit destructor calls and
placement new-expression to change the active member of a union."
Cheers.
Tim.
- Previous message: [llvm-dev] [EXTERNAL] Re: bug is APFloat assignment
- Next message: [llvm-dev] bug is APFloat assignment
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]