On 18:31 Sun 09 Nov , Andrew Haley wrote:
> Zhang Le wrote:
>
> >
> > The other would be make sure the destination register is different from
> > source registers.
> > I have read some docs, but still not sure how to do it.
>
> That's just an earlyclobber. Search for that.
Thank you, Andr
Naveen H.S. wrote:
causing the branch to be based on the output of the bit op rather
than whatever was in cc0 from some previous operation
Yes, the peepholes cause the branch to be based on the output of bit.
However, the peepholes were implemented as they generate new
conditional bit
Hi Jeff,
>> Don't forget to include the ChangeLog.
Thanks a lot for verifying the patch and useful suggestions.
>> causing the branch to be based on the output of the bit op rather
>> than whatever was in cc0 from some previous operation
Yes, the peepholes cause the branch to be based on the ou
Hello
the file in bits/basic_string.tcc call it.
template
template
_CharT*
basic_string<_CharT, _Traits, _Alloc>::
_S_construct(_InIterator __beg, _InIterator __end, const _Alloc& __a,
forward_iterator_tag)
{
#ifndef _GLIBCXX_FULLY_DYNAMIC_STRING
if (__beg
On 19:18 Mon 10 Nov , Zhang Le wrote:
> However, now I think adding a earlyclobber constraint may be the way to go.
> Since it is a less intrusive and more elegant (comparing with my patch above)
> change.
This solution is as easy as adding two bytes (two &s's) to the original patch:
@@ -11,7
On 09:18 Mon 10 Nov , Eric Fisher wrote:
> > So I think one of the possible solution would be to reverse the div.g and
> > teq insn.
> > And I think this is not hard to do, just modify mips_output_division()
> > function.
> > Also I think this is a better solution, since we can save a registe
Zhang Le <[EMAIL PROTECTED]> writes:
> On 19:18 Mon 10 Nov , Zhang Le wrote:
>> However, now I think adding a earlyclobber constraint may be the way to go.
>> Since it is a less intrusive and more elegant (comparing with my patch
>> above) change.
>
> This solution is as easy as adding two byt
"Eric Fisher" <[EMAIL PROTECTED]> writes:
> In mips.md, conditional branch insns are all set with the attribute
> value 'branch'. But floating point instructions such as bc1f will
> reserve falu unit instead of ialu. So there's a problem when you try
> to describe pipeline for 'branch' insns. Defin
Hello all,
While prototyping a port of gcc I think that the RTX is lacking some
information needed to generate machine dependent files. The expression
trees have the correct information and I can likely hack in a quick fix to
pass that information down to the backend. However, I just want to make
We have a system where, when bootstrapping,
gcc is used to output assembly on the host,
and the assembly files are copied to another system,
where they are assembled and linked.
Whether we use GNU as and ld or native/vendor is flexible,
depending on what works and what I care to build.
e.g. AI
Ping?
http://gcc.gnu.org/ml/gcc/2008-10/msg00491.html
> "Jiri" == Jiri Slaby <[EMAIL PROTECTED]> writes:
Jiri> I want to extend cpp to extract some more info (for backward
Jiri> mapping from preprocessed_code into source_code+line+column)
Jiri> into xml while preprocessing and I use gdome2 library. If I try
Jiri> to compile it, it fails due to: [
Hi,
I am using GCC version 4.3.0 on Linux FC 9. I found following a wired situation:
In a test.cpp there is a statement:
uint16_t so = ::htons(a); // line 168
It compiled fine if I use -g. But when I changed the -g to -O, it
broken to errors:
g++ -O -Wall -Wundef -Wabi -Wextra -Wunused -Wconv
Hello,
Anyone could tell how to be a gcc maintainer? Is there any
requirement? Actually, my previous work are all not based on the gcc
trunk. So no patch submitted. Anyway, it's cool to contribute :-)
Thanks.
Eric Fisher
2008-11-11
[EMAIL PROTECTED] writes:
> While prototyping a port of gcc I think that the RTX is lacking some
> information needed to generate machine dependent files. The expression
> trees have the correct information and I can likely hack in a quick fix to
> pass that information down to the backend. Howeve
"Eric Fisher" <[EMAIL PROTECTED]> writes:
> Anyone could tell how to be a gcc maintainer? Is there any
> requirement? Actually, my previous work are all not based on the gcc
> trunk. So no patch submitted. Anyway, it's cool to contribute :-)
The usual procedure is to write a bunch of good patches
16 matches
Mail list logo
