search for: sarrasin

Hi all, The DAGCombiner pass actually runs even if the optimize level is set to None. This can result in incorrect debug information or unexpected stepping/debugging experience. Not to mention that having good stepping/debugging experience is the major reason to compile at /O0. I recently suggested a patch to disable one specific DAG combine at /O0 that broke stepping on a particular case

Hi, I am looking at the Type Based Alias Analysis and I am trying to understand why, from what I see, pointsToConstantMemory() never returns true. It seems that this information should come from the TBAA metadata, in which the Access Tag has an optional 4th field to specify this information. "Access tags are represented as MDNode s with either 3 or 4 operands. The first operand is an

...> DEBUG(dbgs() << "\nCombining: "; N->dump(&DAG)); > > // Add any operands of the new node which have not yet been combined to the > > >   <> > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Marianne Mailhot-Sarrasin via llvm-dev > Sent: Friday, May 13, 2016 12:21 PM > To: llvm-dev at lists.llvm.org > Subject: [llvm-dev] [RFC] Disabling DAG combines in /O0 > > Hi all, > > The DAGCombiner pass actually runs even if the optimize level is set to None. This can result in incorrect debug inf...