search for: praticularly

Displaying 7 results from an estimated 7 matches for "praticularly".

Did you mean: particularly
2016 Mar 21
7
Need help with code generation
...rash "llc -filetype=obj". The fact that it is considered a > bug doesn't mean much if there is no coordinated effort to fix them. > I think it does, actually - that patches will be accepted to fix pretty much any crash in LLVM. (llc isn't a user facing tool, so that's a praticularly low priority - but as a general library (I assume your example also crashes Clang, which would be where this would surface in a more important way) it's pretty well accepted that crashes are bugs, I think) > Right now lld is already harder to crash than llvm. We are just being > honest...
2016 Mar 21
3
Need help with code generation
...t that it is considered a > >> bug doesn't mean much if there is no coordinated effort to fix them. > > > > > > I think it does, actually - that patches will be accepted to fix pretty > much any crash in LLVM. (llc isn't a user facing tool, so that's a > praticularly low priority - > > I am pretty sure clang crashes if you translate the above example to C. > > Philosophical question: what is the difference of a non bug and a bug of > such low priority that it is never fixed? > One where contributors are encouraged to provide patches to fix th...
2016 Mar 21
2
Need help with code generation
...t is considered a >>> bug doesn't mean much if there is no coordinated effort to fix them. >>> >> >> I think it does, actually - that patches will be accepted to fix pretty >> much any crash in LLVM. (llc isn't a user facing tool, so that's a >> praticularly low priority - but as a general library (I assume your example >> also crashes Clang, which would be where this would surface in a more >> important way) it's pretty well accepted that crashes are bugs, I think) >> >> >>> Right now lld is already harder to crash...
2016 Mar 21
2
Need help with code generation
...'t mean much if there is no coordinated effort to fix them. >>>>> >>>> >>>> I think it does, actually - that patches will be accepted to fix pretty >>>> much any crash in LLVM. (llc isn't a user facing tool, so that's a >>>> praticularly low priority - but as a general library (I assume your example >>>> also crashes Clang, which would be where this would surface in a more >>>> important way) it's pretty well accepted that crashes are bugs, I think) >>>> >>>> >>>>>...
2016 Mar 21
2
Need help with code generation
...ted effort to fix them. >>>>>>> >>>>>> >>>>>> I think it does, actually - that patches will be accepted to fix >>>>>> pretty much any crash in LLVM. (llc isn't a user facing tool, so that's a >>>>>> praticularly low priority - but as a general library (I assume your example >>>>>> also crashes Clang, which would be where this would surface in a more >>>>>> important way) it's pretty well accepted that crashes are bugs, I think) >>>>>> >>>&g...
2016 Mar 21
4
Need help with code generation
...t is considered a >>> bug doesn't mean much if there is no coordinated effort to fix them. >>> >> >> I think it does, actually - that patches will be accepted to fix pretty >> much any crash in LLVM. (llc isn't a user facing tool, so that's a >> praticularly low priority - but as a general library (I assume your example >> also crashes Clang, which would be where this would surface in a more >> important way) it's pretty well accepted that crashes are bugs, I think) >> >> >>> Right now lld is already harder to crash...
2016 Mar 21
2
Need help with code generation
> My understanding is that clang and llvm themselves are designed this way > (crash when the unexpected happens). I don't think so. I'd view any Clang crash as a bug (probably to be prioritised below silent CodeGen and many others, but not "working as designed"). > For example the fact that clang forks itself to be able to report diagnostics That seems like just