search for: kpszeniczny

Displaying 10 results from an estimated 10 matches for "kpszeniczny".

Did you mean: pszeniczny
2019 Oct 02
2
[RFC] Propeller: A frame work for Post Link Optimizations
On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev < llvm-dev at lists.llvm.org> wrote: > *Pessimization/overhead for stack unwinding used by system-wide profilers > and > for exception handling* > > Larger CFI programs put an extra burden on unwinding at runtime as more CFI > (and thus native) instructions have to be executed. This will cause more > overhead
2019 Oct 02
4
[RFC] Propeller: A frame work for Post Link Optimizations
...that .eh_frame_hdr, an allocatable > section, > > will be bloated too. This will increase the FDE lookup time. I don’t see > .eh_frame_hdr > > being mentioned in the proposal. > > > > Maksim > > > > On 10/2/19, 12:20 PM, "Krzysztof Pszeniczny" <kpszeniczny at google.com> > wrote: > > > > > > > > On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > *Pessimization/overhead for stack unwinding used by system-wide profilers > and > for exception handling...
2019 Oct 07
2
[RFC] Propeller: A frame work for Post Link Optimizations
...will increase the FDE lookup time. I don’t see .eh_frame_hdr > >> > >> being mentioned in the proposal. > >> > >> > >> > >> Maksim > >> > >> > >> > >> On 10/2/19, 12:20 PM, "Krzysztof Pszeniczny" <kpszeniczny at google.com> wrote: > >> > >> > >> > >> > >> > >> > >> > >> On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> > >> *Pessimization/overhead for sta...
2018 Dec 02
4
RFC: Supported Optimizations attribute
...ease check out our RFC: Supported Optimizations attribute https://docs.google.com/document/d/1s0n-JVaSNML1Z9SCZVg2bgisxswIJAK2Tp9DahucW10/edit?usp=sharing Pasting it here for the record: RFC: supported_optimizations attribute Piotr Padlewski - piotr.padlewski at gmail.com Krzysztof Pszeniczny - kpszeniczny at google.com December 2018 Introduction Sometimes a possible class of optimizations requires very precise use of metadata and/or intrinsics, at least to achieve a clean implementation thereof. Our primary example is devirtualization[RFC: Devirtualization v2 <https://docs.google.com/document/...
2019 Oct 08
2
[RFC] Propeller: A frame work for Post Link Optimizations
...>> being mentioned in the proposal. > > > >> > > > >> > > > >> > > > >> Maksim > > > >> > > > >> > > > >> > > > >> On 10/2/19, 12:20 PM, "Krzysztof Pszeniczny" <kpszeniczny at google.com> wrote: > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev <llvm-dev at lists...
2019 Oct 17
2
[RFC] Propeller: A frame work for Post Link Optimizations
...that .eh_frame_hdr, an allocatable > section, > > will be bloated too. This will increase the FDE lookup time. I don’t see > .eh_frame_hdr > > being mentioned in the proposal. > > > > Maksim > > > > On 10/2/19, 12:20 PM, "Krzysztof Pszeniczny" <kpszeniczny at google.com> > wrote: > > > > > > > > On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > *Pessimization/overhead for stack unwinding used by system-wide profilers > and > for exception handling...
2019 Oct 11
2
[RFC] Propeller: A frame work for Post Link Optimizations
...that .eh_frame_hdr, an allocatable > section, > > will be bloated too. This will increase the FDE lookup time. I don’t see > .eh_frame_hdr > > being mentioned in the proposal. > > > > Maksim > > > > On 10/2/19, 12:20 PM, "Krzysztof Pszeniczny" <kpszeniczny at google.com> > wrote: > > > > > > > > On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > *Pessimization/overhead for stack unwinding used by system-wide profilers > and > for exception handling...
2019 Oct 14
2
[RFC] Propeller: A frame work for Post Link Optimizations
...l increase the FDE lookup time. I don’t see >>> .eh_frame_hdr >>> >>> being mentioned in the proposal. >>> >>> >>> >>> Maksim >>> >>> >>> >>> On 10/2/19, 12:20 PM, "Krzysztof Pszeniczny" <kpszeniczny at google.com> >>> wrote: >>> >>> >>> >>> >>> >>> >>> >>> On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev < >>> llvm-dev at lists.llvm.org> wrote: >>> >>> *Pessimization...
2019 Oct 18
3
[RFC] Propeller: A frame work for Post Link Optimizations
...that .eh_frame_hdr, an allocatable > section, > > will be bloated too. This will increase the FDE lookup time. I don’t see > .eh_frame_hdr > > being mentioned in the proposal. > > > > Maksim > > > > On 10/2/19, 12:20 PM, "Krzysztof Pszeniczny" <kpszeniczny at google.com> > wrote: > > > > > > > > On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > *Pessimization/overhead for stack unwinding used by system-wide profilers > and > for exception handling...
2019 Oct 22
2
[RFC] Propeller: A frame work for Post Link Optimizations
...that .eh_frame_hdr, an allocatable > section, > > will be bloated too. This will increase the FDE lookup time. I don’t see > .eh_frame_hdr > > being mentioned in the proposal. > > > > Maksim > > > > On 10/2/19, 12:20 PM, "Krzysztof Pszeniczny" <kpszeniczny at google.com> > wrote: > > > > > > > > On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > *Pessimization/overhead for stack unwinding used by system-wide profilers > and > for exception handling...