On Tue, 2014-11-25 at 10:15 -0700, Jeff Law wrote:
> On 11/25/14 10:14, Segher Boessenkool wrote:
> > On Tue, Nov 25, 2014 at 09:44:35AM -0700, Jeff Law wrote:
> >> On 11/24/14 20:37, Segher Boessenkool wrote:
> >>> `lcc' is not an insn but just a pattern. This caused a build error in
> >>> libgcc
On 11/25/14 10:14, Segher Boessenkool wrote:
On Tue, Nov 25, 2014 at 09:44:35AM -0700, Jeff Law wrote:
On 11/24/14 20:37, Segher Boessenkool wrote:
`lcc' is not an insn but just a pattern. This caused a build error in
libgcc.
A good example of a case that would have been caught if we get to
On Tue, Nov 25, 2014 at 09:44:35AM -0700, Jeff Law wrote:
> On 11/24/14 20:37, Segher Boessenkool wrote:
> >`lcc' is not an insn but just a pattern. This caused a build error in
> >libgcc.
> A good example of a case that would have been caught if we get to a
> point where stuff in the insn chain
On 11/24/14 20:37, Segher Boessenkool wrote:
`lcc' is not an insn but just a pattern. This caused a build error in
libgcc.
Tested with a cross compiler build (which fails without and succeeds
with the patch). Not tested much more; this compiler really likes to
ICE, something with ipa-icf.
Is t
`lcc' is not an insn but just a pattern. This caused a build error in
libgcc.
Tested with a cross compiler build (which fails without and succeeds
with the patch). Not tested much more; this compiler really likes to
ICE, something with ipa-icf.
Is this okay for trunk?
Segher
2014-11-24 Segh
