Hi,
The patch queue http://www.dberlin.org/patches seems to be down. I
understand that Daniel is very busy and he is making some changes to
his site. However, I would argue that the queue was being quite
successful and provided a valuable service for many GCC developers. I
also provided a place to
could a new bie say goodbye to you?
wave~~~
Per Bothner 写道:
I'm sorry to announce that I'm resigning from the GCC Steering
Committee. I have been embarrassingly inactive in both GCC development
and on the committee the last few years. There doesn't seem to be
any likelihood that this will cha
I'm sorry to announce that I'm resigning from the GCC Steering
Committee. I have been embarrassingly inactive in both GCC development
and on the committee the last few years. There doesn't seem to be
any likelihood that this will change in the foreseeable future,
even less so now that I have a "
Hi,
Am new to unicode programming and was playing with the following program..
#include
#include
#include
int main(int narg, char *varg[])
{
wprintf(L"%ls\n", L"This is a test of wprintf");
printf("%s\n", "This is a test of printf");
return 0;
}
Compiling it using
Boris Boesler <[EMAIL PROTECTED]> writes:
> I'm trying to allocate a scratch register: write immediate constant
> into scratch register r, write register r into memory
>
> ;; write imm into memory
> (define_insn_and_split "mov_imm_by_store"
>[(set (match_operand:I8I16 0 "memory_operand"
Snapshot gcc-4.2-20080109 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20080109/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.2 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
> I find this somewhat unclear - It seems to imply that HARD_REGNO_NREGS may be
> called even when HARD_REGNO_MODE_OK returns false.
That's exactly the case that's happening for m32c, and for which the
new text is needed.
> @defmac HARD_REGNO_NREGS (@var{regno}, @var{mode})
> A C expression for the number of consecutive hard registers, starting
> at register number @var{regno}, required to hold a value of mode
> [EMAIL PROTECTED]
> [EMAIL PROTECTED] This macro must never return zero, even if a register
> +cannot
How about this change, then? (I'm still testing the m32c change, too)
2008-01-09 DJ Delorie <[EMAIL PROTECTED]>
* doc/tm.texi (HARD_REGNO_NREGS): Note that this macro must not
return zero.
Index: doc/tm.texi
===
DJ Delorie wrote:
Are there any ports besides m32c that have registers which can hold HI
(or SI I suppose) but not QI values?
IA-64 has branch registers that are only allowed to hold DImode values.
We use CANNOT_CHANGE_MODE_CLASS to enforce this.
On x86, the vector registers can hold SImode
Ian Lance Taylor wrote:
> "Manuel López-Ibáñez" <[EMAIL PROTECTED]> writes:
>
>> Of course there is a third option:
>>
>> * Make pedwarns warnings by default unless -Werror or
>> --pedantic-errors are given (just like the C front-end).
>
> This makes sense to me. I have never understood why it i
DJ Delorie wrote:
Which assumption is wrong? That hard_regno_nregs can be zero (m32c),
or that hard_regno_nregs will never be zero (rtlanal)?
I would say the m32c port is wrong. HARD_REGNO_MODE_OK indicates
whether a register can hold a mode. HARD_REGNO_NREGS indicates how many
registers w
Hi!
I'm trying to allocate a scratch register: write immediate constant
into scratch register r, write register r into memory
;; write imm into memory
(define_insn_and_split "mov_imm_by_store"
[(set (match_operand:I8I16 0 "memory_operand""=m")
(match_operand:I8I16 1 "immediate_
Andrew Pinski wrote:
> constaint
*consistent*
Paolo.
On 1/9/08, Benjamin Kosnik <[EMAIL PROTECTED]> wrote:
> Me too. The current error behavior just seems gratuitous. What was the
> rationale for this change to error instead of warn? I am having
> problems locating this discussion on gcc-patches.
The recent preprocessor change or the older front-end
>> Of course there is a third option:
>> * Make pedwarns warnings by default unless -Werror or
>> --pedantic-errors are given (just like the C front-end).
>This makes sense to me. I have never understood why it is a good idea
>for the C++ and C frontends to differ in this way.
Me too. The curre
DJ Delorie <[EMAIL PROTECTED]> writes:
> > I would first ask why subreg_get_info is being called with ymode ==
> > QImode for a hard register which can not hold QImode. That implies
> > that there is a QImode value in the register, which you say is
> > invalid.
>
> Are there any ports besides m3
tian xiaonan <[EMAIL PROTECTED]> writes:
> Hi, All. I don't know How to regenerate a new
> configure file while added new target on config.sub,
> and gcc/config.gcc. I am a newcomer in using GCC.
Changing config.sub and/or gcc/config.gcc does not require
regenerating the configure script.
If yo
Benjamin Kosnik <[EMAIL PROTECTED]> writes:
> As such, I'd like to get a general indication from the greater GCC
> community as to this plan. Does this document seem like a good idea?
> (Previously, we've left this kind of document to the user community.
> Often the passage of time has not been pa
"Manuel López-Ibáñez" <[EMAIL PROTECTED]> writes:
> Of course there is a third option:
>
> * Make pedwarns warnings by default unless -Werror or
> --pedantic-errors are given (just like the C front-end).
This makes sense to me. I have never understood why it is a good idea
for the C++ and C fro
> I would first ask why subreg_get_info is being called with ymode ==
> QImode for a hard register which can not hold QImode. That implies
> that there is a QImode value in the register, which you say is
> invalid.
Are there any ports besides m32c that have registers which can hold HI
(or SI I s
DJ Delorie <[EMAIL PROTECTED]> writes:
> In rtlanal.c we have these lines:
>
> nregs_ymode = hard_regno_nregs[xregno][ymode];
> ...
> && (GET_MODE_SIZE (ymode) % nregs_ymode) == 0)
>
> The m32c cc1 crashes here because xregno is 1 and ymode is QI, and
> register 1 cannot hold a QI valu
Not at all!!! -fpermissive can (in weird cases, agreed) change code
generation. I'm pretty sure you don't want to risk that only to silence
an error.
What? That doesn't make any sense. And it is certainly not documented
in the manual. I will be very interested in an example, no matter how
wei
> To have a better chance to find the issue could you anwser these question?
I'll let J. answer these himself, since I have no direct experience of
the bug myself (no Win64 machine), but...
> a) Does this happens on a cross compiler, too?
I doubt it, since he sees the bug even on trivial program
On 09/01/2008, Paolo Bonzini <[EMAIL PROTECTED]> wrote:
> Andrew Pinski wrote:
> > On 1/8/08, Ismail Dönmez <[EMAIL PROTECTED]> wrote:
> >> Oh that clears up my confusion. So the right fix would be downgrading this
> >> redefinition problem to be pedwarn instead. But I see no point in creating
> >
> [for [EMAIL PROTECTED] and [EMAIL PROTECTED] readers, seeshort thread
> starting at http://gcc.gnu.org/ml/fortran/2008-01/msg00103.html]
>
> > Gcc gets the similar problem. It only works without optimization.
> It seems not a problem with gfortran.
>
> OK, then it'd be more appropriate to ask
[for [EMAIL PROTECTED] and [EMAIL PROTECTED] readers, seeshort thread
starting at http://gcc.gnu.org/ml/fortran/2008-01/msg00103.html]
> Gcc gets the similar problem. It only works without optimization. It seems
> not a problem with gfortran.
OK, then it'd be more appropriate to ask the mingw m
Andrew Pinski wrote:
On 1/8/08, Ismail Dönmez <[EMAIL PROTECTED]> wrote:
Oh that clears up my confusion. So the right fix would be downgrading this
redefinition problem to be pedwarn instead. But I see no point in creating a
bug report if its just gonna be closed as invalid, so I hope we can dis
Benjamin Kosnik writes:
>
> > Attached is a rough cut of a detailed portability document
>
> I also put this up here temporarily:
>
> http://people.redhat.com/~bkoz/porting_to_gcc43.html
The "Java issues" part isn't quite right. It turns out that the java
1.2 problem with the new gcj is
29 matches
Mail list logo
