Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2018-07-03 Thread Alex Peshkoff via Firebird-devel
On 03.07.2018 12:36, Dimitry Sibiryakov wrote: 02.07.2018 16:01, Alex Peshkoff via Firebird-devel wrote: Should 16-byte alignment be enforced only for x64 builds or for x86 too?   I would invite it for 32 bits too as it would let to use AES and other 128 bits CPU commands without need to

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2018-07-02 Thread Alex Peshkoff via Firebird-devel
On 16.04.2018 15:59, Alex Peshkoff via Firebird-devel wrote: On 04/16/18 15:08, Stephan Bergmann wrote: On 17/02/17 11:48, Alex Peshkoff wrote: On 02/16/17 15:52, Stephan Bergmann wrote: Forgive me if this has already been discussed or even fixed in later versions:  At least the Firebird 3.0

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2018-04-16 Thread Alex Peshkoff via Firebird-devel
On 04/16/18 15:08, Stephan Bergmann wrote: On 17/02/17 11:48, Alex Peshkoff wrote: On 02/16/17 15:52, Stephan Bergmann wrote: Forgive me if this has already been discussed or even fixed in later versions:  At least the Firebird 3.0 we build as part of LibreOffice defines global operator new

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2018-04-16 Thread Stephan Bergmann
On 17/02/17 11:48, Alex Peshkoff wrote: On 02/16/17 15:52, Stephan Bergmann wrote: Forgive me if this has already been discussed or even fixed in later versions: At least the Firebird 3.0 we build as part of LibreOffice defines global operator new replacement functions in

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2017-02-17 Thread Paul Beach
On 17/02/2017 09:39, Stephan Bergmann wrote: > On 02/17/2017 12:24 PM, Alex Peshkoff wrote: >> On 02/17/17 14:15, Stephan Bergmann wrote: >> >> This idea seems to be much better than DEBUG_GDS_ALLOC: >> >>> Since LibreOffice builds intended for widespread distribution are on >>> Linux usually done

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2017-02-17 Thread Adriano dos Santos Fernandes
On 17/02/2017 09:39, Stephan Bergmann wrote: > On 02/17/2017 12:24 PM, Alex Peshkoff wrote: >> On 02/17/17 14:15, Stephan Bergmann wrote: >> >> This idea seems to be much better than DEBUG_GDS_ALLOC: >> >>> Since LibreOffice builds intended for widespread distribution are on >>> Linux usually done

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2017-02-17 Thread Stephan Bergmann
On 02/17/2017 12:24 PM, Alex Peshkoff wrote: > On 02/17/17 14:15, Stephan Bergmann wrote: > > This idea seems to be much better than DEBUG_GDS_ALLOC: > >> Since LibreOffice builds intended for widespread distribution are on >> Linux usually done with GCC not Clang, this shouldn't have a

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2017-02-17 Thread Stephan Bergmann
On 02/17/2017 12:21 PM, Alex Peshkoff wrote: > On 02/17/17 14:15, Stephan Bergmann wrote: >> On 02/17/2017 11:48 AM, Alex Peshkoff wrote: >>> On 02/16/17 15:52, Stephan Bergmann wrote: Forgive me if this has already been discussed or even fixed in later versions: At least the Firebird

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2017-02-17 Thread Alex Peshkoff
On 02/17/17 14:15, Stephan Bergmann wrote: This idea seems to be much better than DEBUG_GDS_ALLOC: > Since LibreOffice builds intended for widespread distribution are on > Linux usually done with GCC not Clang, this shouldn't have a performance > impact.) But what makes me surprised - I know

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2017-02-17 Thread Alex Peshkoff
On 02/17/17 14:15, Stephan Bergmann wrote: > On 02/17/2017 11:48 AM, Alex Peshkoff wrote: >> On 02/16/17 15:52, Stephan Bergmann wrote: >>> Forgive me if this has already been discussed or even fixed in later >>> versions: At least the Firebird 3.0 we build as part of LibreOffice >>> defines

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2017-02-17 Thread Stephan Bergmann
On 02/17/2017 11:48 AM, Alex Peshkoff wrote: > On 02/16/17 15:52, Stephan Bergmann wrote: >> Forgive me if this has already been discussed or even fixed in later >> versions: At least the Firebird 3.0 we build as part of LibreOffice >> defines global operator new replacement functions in >>

Re: [Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2017-02-17 Thread Alex Peshkoff
On 02/16/17 15:52, Stephan Bergmann wrote: > Forgive me if this has already been discussed or even fixed in later > versions: At least the Firebird 3.0 we build as part of LibreOffice > defines global operator new replacement functions in > src/common/classes/alloc.h (forwarding to MemoryPool)

[Firebird-devel] alloc.h global operator new replacement violating alignment requirements

2017-02-16 Thread Stephan Bergmann
Forgive me if this has already been discussed or even fixed in later versions: At least the Firebird 3.0 we build as part of LibreOffice defines global operator new replacement functions in src/common/classes/alloc.h (forwarding to MemoryPool) that do not in general fulfil the alignment