On Thu, Jan 15, 2015 at 8:30 AM, H.J. Lu wrote:
> On Thu, Jan 15, 2015 at 8:24 AM, Mike Stump wrote:
>> So, I was hoping that someone would step forward and review this. I’d like
>> for a reviewer to consider, is this the type of error messages we want to
>> vend to the poor user? It strikes
On Thu, Jan 15, 2015 at 8:24 AM, Mike Stump wrote:
> So, I was hoping that someone would step forward and review this. I’d like
> for a reviewer to consider, is this the type of error messages we want to
> vend to the poor user? It strikes me as, well, icky. Should -fPIE imply
> -fPIC?
It i
So, I was hoping that someone would step forward and review this. I’d like for
a reviewer to consider, is this the type of error messages we want to vend to
the poor user? It strikes me as, well, icky. Should -fPIE imply -fPIC?
Exclusive of that issue, the patch is fine.
On Jan 11, 2015, at
g++.dg/other/anon5.C is expected to fail to link. On Linux/x86 with PIE,
there are additional messages linker:
[hjl@gnu-tools-1 gcc]$ g++ -fPIE -pie
/export/gnu/import/git/sources/gcc/gcc/testsuite/g++.dg/other/anon5.C
/tmp/ccwg53fj.o: In function `f()': anon5.C:(.text+0x7): undefined reference
