search for: pr21466

...ay it is still way easier to crash llvm than lld. I posted two crashes with just what I noticed going on the list. No one even posted an ELF that would crash lld. It is really annoying how much people care about "security" to criticize my work, but never enough to send a patch. llvm.org/pr21466 is open since Nov 2014. That is on the side of the project that should be handling broken files. Would it end this thread if I went that way? Just say that there are bugs in lld and just not fix them for over a year? Cheers, Rafael

...to the stated policy that it's intentional that LLD > would crash/UB on certain inputs. We're debating that policy/intention. > > >> It is really annoying how much people care about "security" to >> criticize my work, but never enough to send a patch. llvm.org/pr21466 >> is open since Nov 2014. That is on the side of the project that should >> be handling broken files. > > >> Would it end this thread if I went that way? Just say that there are >> bugs in lld and just not fix them for over a year? >> > > It would make a b...

..., we were responding to the stated policy that it's intentional that LLD would crash/UB on certain inputs. We're debating that policy/intention. > It is really annoying how much people care about "security" to > criticize my work, but never enough to send a patch. llvm.org/pr21466 > is open since Nov 2014. That is on the side of the project that should > be handling broken files. > Would it end this thread if I went that way? Just say that there are > bugs in lld and just not fix them for over a year? > It would make a big difference if it was "Yes, th...

...were responding to the stated policy that it's intentional that LLD would crash/UB on certain inputs. We're debating that policy/intention. > > It is really annoying how much people care about "security" to > criticize my work, but never enough to send a patch. llvm.org/pr21466 <http://llvm.org/pr21466> > is open since Nov 2014. That is on the side of the project that should > be handling broken files. > > Would it end this thread if I went that way? Just say that there are > bugs in lld and just not fix them for over a year? > > It would make...

...to the stated policy that it's intentional > that LLD would crash/UB on certain inputs. We're debating that > policy/intention. > > > It is really annoying how much people care about "security" to > criticize my work, but never enough to send a patch. llvm.org/pr21466 > is open since Nov 2014. That is on the side of the project that > should > be handling broken files. > > > Would it end this thread if I went that way? Just say that there are > bugs in lld and just not fix them for over a year? > > > > It would make a big di...

...use we seem to be debating whether we'd actively reject a patch to fix such issues, not how important they are to us to fix. Thanks again, Hal > > It is really annoying how much people care about "security" to > criticize my work, but never enough to send a patch. llvm.org/pr21466 > is open since Nov 2014. That is on the side of the project that > should > be handling broken files. > > Would it end this thread if I went that way? Just say that there are > bugs in lld and just not fix them for over a year? > > Cheers, > Rafael > -- Hal Finke...

----- Original Message ----- > From: "Rafael Espíndola via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Mehdi Amini" <mehdi.amini at apple.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "Bruce Hoult" <bruce at hoult.org> > Sent: Monday, March 21, 2016 8:24:16 PM > Subject: Re: [llvm-dev] Need help with code

>> >> * I don't want to trade my time implementing stuff users will see (linker script, debug index, speed) for things users will not. > > > Don't you think that you are somehow trading your time for other people's time when they'll have to build other features on top of the codebase? > I understand you're putting the cursor toward end-users facing