Displaying 9 results from an estimated 9 matches for "rtrieu".
Did you mean:
trieu
2015 Sep 29
2
Fwd: buildbot failure in LLVM on clang-ppc64-elf-linux2
...Papin <guillaume.papin at epitech.eu>, Matt Arsenault <
Matthew.Arsenault at amd.com>, Matthias Braun <matze at braunis.de>, Philip
Reames <listmail at philipreames.com>, Piotr Padlewski <prazek at google.com>,
Reid Kleckner <rnk at google.com>, Richard Trieu <rtrieu at google.com>, Sanjay
Patel <spatel at rotateright.com>, Sanjoy Das <sanjoy at playingwithpointers.com>,
Sean Silva <chisophugis at gmail.com>, Weiming Zhao <weimingz at codeaurora.org>
Cc: gkistanova at gmail.com
The Buildbot has detected a new failure on builder clan...
2015 Sep 29
3
Fwd: buildbot failure in LLVM on clang-ppc64-elf-linux2
...> Matt Arsenault < Matthew.Arsenault at amd.com >, Matthias Braun <
> > matze at braunis.de >, Philip Reames < listmail at philipreames.com >,
> > Piotr Padlewski < prazek at google.com >, Reid Kleckner <
> > rnk at google.com >, Richard Trieu < rtrieu at google.com >, Sanjay Patel
> > < spatel at rotateright.com >, Sanjoy Das <
> > sanjoy at playingwithpointers.com >, Sean Silva < chisophugis at gmail.com
> > >, Weiming Zhao < weimingz at codeaurora.org >
> > Cc: gkistanova at gmail.com
> >...
2015 Jan 12
2
[LLVMdev] buildbot failure in LLVM on ppc64le-sanitizer
...;
> Build Reason: scheduler
> Build Source Stamp: [branch trunk] 225670
> Blamelist: ab,abataev,alexfh,artagnon,benlangmuir,chandlerc,chapuni,compnerd,dexonsmith,djasper,dsanders,ehsan,eugenis,foad,gribozavr,hfinkel,jhibbits,jkolek,joerg,majnemer,matze,nathan,rafael,rdivacky,rksimon,rsmith,rtrieu,sanjoy,seurer,spatel,timurrrr,tomatabacu,tstellar
>
> BUILD FAILED: failed annotate
>
> sincerely,
> -The Buildbot
2018 Sep 13
2
New warnings when building trunk with GCC 9
Hello,
GCC 9.0 introduces a new warning checkers and some of them found possible
issues in LLVM.
In file included from
/home/davidbolvansky/trunk/llvm/include/llvm/Analysis/LazyCallGraph.h:38,
from
/home/davidbolvansky/trunk/llvm/unittests/Analysis/LazyCallGraphTest.cpp:10:
/home/davidbolvansky/trunk/llvm/include/llvm/ADT/ArrayRef.h: In
instantiation of
2012 Aug 22
1
[LLVMdev] buildbot failure in LLVM on clang-native-mingw64-win7
...topper,d0k,dblaikie,ddunbar,delesley,dgregor,djasper,dyatkovskiy,echristo,efriedma,evancheng,fjahanian,gps,gribozavr,grosbach,grosser,hanm,hans,hliao,jacksprat,jaykang10,jrose,jush,kcc,klimek,kremenek,matthewbg,mcrosier,mspencer,nadav,nicholas,panzer,pranavb,rafael,rdivacky,resistor,rjmccall,rsmith,rtrieu,spop,spyffe,stoklund,tbrethou,tnorthover,victorm,void,zaks
>
> BUILD FAILED: failed clang-test
>
> sincerely,
> -The Buildbot
>
>
>
2013 Aug 30
1
[LLVMdev] buildbot failure in LLVM on clang-amd64-openbsd
...ey,jrose,jtsoftware,kevinqin,klimek,kremenek,kuba,labath,lattner,lhames,logan,lvoufo,majnemer,mgottesman,mkuper,mpopa,mren,mspencer,nadav,nicholas,nico,olesalscheider,papin_g,pcc,predmond,rafael,rdivacky,redstar,rengolin,resistor,revane,ributzka,rikka,rkotler,rlytton,rmitton,rnk,row,rsandifo,rsmith,rtrieu,rudkx,ruiu,samsonov,sbaranga,sbenza,sdt,sepavloff,shuxin_yang,silvas,stephenwlin,stoklund,sylvestre,tasiraj,timurrrr,tnorthover,tstellar,uweigand,venkatra,vmedic,void,whunt,wpan,wschmidt,ygao,yjiang
>
> BUILD FAILED: failed compile
>
> sincerely,
> -The Buildbot
>
>
>
2018 Sep 25
3
[cfe-dev] New warnings when building trunk with GCC 9
...getA() { return A(1); }
B run1() {
A a = getA();
return std::move(a);
}
B run2() {
A a = getA();
return a;
}
int main() {
std::cout << "with move:\n";
run1();
std::cout << "no move:\n";
run2();
}
On Tue, Sep 18, 2018 at 4:07 PM Richard Trieu <rtrieu at google.com> wrote:
> I'll look into the pessimizing move warning, then after that, the
> deprecated copy warning.
>
> On Sun, Sep 16, 2018 at 10:41 AM Richard Smith <richard at metafoo.co.uk>
> wrote:
>
>> Yes, we should produce this warning in C++11 mode to...
2018 Sep 16
2
[cfe-dev] New warnings when building trunk with GCC 9
Yes, we should produce this warning in C++11 mode too. (I could be
misrecalling, but I think the rationale for the current behaviour is based
on historical GCC behaviour.)
On Sun, 16 Sep 2018, 10:04 David Blaikie via cfe-dev, <
cfe-dev at lists.llvm.org> wrote:
> Fair point made on that thread - that this is a DR, so technically the
> std::move is pessimizing even in C++11 mode.
2019 Feb 25
2
[Sanitizers] Platforms that don't support stack unwinding
Thank you for the explanation, Ben!
I realized I didn’t give enough context for my question:
As you noted, the slow/fast unwinder can only do its work if there is enough (runtime) information.
Otherwise stack printing usually does exactly what you suggested: printing the one frame corresponding to the recent pc.
When I asked if “platforms are required to at least support one kind of unwinder” I