Hello,
I tried to compile the gcc-melt branch from svn, but i get the following error:
make warmelt1
make[4]: Entering directory `/home/wolfgang/gcc-melt/objects/gcc'
date +"/* empty-file-for-melt.c %c */" > empty-file-for-melt.c-tmp
/bin/bash ../../melt-branch/gcc/../mo
Original-Nachricht
> Datum: Tue, 25 May 2010 16:20:14 +0200
> Von: Basile Starynkevitch
> An: Wolfgang
> CC: gcc@gcc.gnu.org
> Betreff: Re: Melt-building problem
> On Tue, 2010-05-25 at 12:03 +0200, Wolfgang wrote:
> > Hello,
> >
> > I
--disable-bootstrap
Thread model: posix
gcc version 4.6.0 20100406 (experimental) (GCC)
Now i can not reproduce the error any more
Thanks a lot for your help
Wolfgang
> > >
> > > > but i get the following error:
> > > >
> > > >
> > &g
to start. I'm able to walk throug the Gimple-Statements and debug it, but i'm
not able to insert something.
Is there any source-code available?
Thanks
Wolfgang
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
some of the code translating tree nodes into rtxes like
some functions found in builtins.c worry about the re-evaluation of
arguments and insert plenty of SAVE_EXPRs. Why is that necessary?
With best regards,
Wolfgang Gellerich
---
Dr. Wolfgang Gellerich
IBM Deutschland Entwicklung GmbH
SchÃ
rt to
believe that I may be the only one seeing this. Anyone any explanations?
Thanks
Wolfgang
PS: System is "Linux terra.ices.utexas.edu 2.4.25-13mdkenterprise #1 SMP
Tue Jan 18 14:02:17 MST 2005 i686 unknown unknown GNU/Linux", the
bootstr
Isn't this the normal always_inline problem from the kernel headers?
Yes, good spot. Thanks for the help!
W.
-
Wolfgang Bangerth email:[EMAIL PROTECTED]
www:
class information (as
opposed to structure member information), but the aliasing code what have to
know about the difference.
Best
Wolfgang
-
Wolfgang Bangerth email:[EMAIL PROTECTED]
www: http://www.ices.utexas.edu/~bangerth/
s of
the only remaining stack object, of type S, to g().
The community at large may have more experience with such "as-if" related
questions. It would be interested to know whether the scalarizers in gcc
realize, for example, whether they can/can't get rid of
probably some other places, there doesn't seem to be any documentation of
what this flag does etc.
Is there someone who can give me the gist of its meaning? If I get a
reasonable explanation, I may even be willing to write a blurb for the
manual...
Best
Wol
rtant for the binary interface (ELF here,
or?) to have that feature as well. What do you think?
Regards,
Wolfgang Roemer
Hello Michael,
first of all: Thanks for the fast reply!
On Thu Oct 06, 2005 10:33, you wrote:
>> [..]
>>
>> It's a feature. It is undefined behavior to have conflicting declarations
>> in different translation units.
>> [...]
Well, but shouldn't there at least be a warning during linking!?
>
Hello,
so it seems as if it would be best if I post that to the binutils mailing
list. Agreed?
WR
On Thu Oct 06, 2005 11:57, Robert Dewar wrote:
>> Michael Veksler wrote:
>> > It sounds as if the symbol is still "maximum" and it is annotated with
>> > its type (something like debug informati
nimum). The assertion will show that.
I tested that on Windows with Visual C++ as well and there main.obj doesn't
link because the variable type is part of the symbol name and everthing is
fine.
I think it would be very very important for the binary interface to have that
feature as well.
Regards,
Wolfgang Roemer
On Thu Oct 06, 2005 14:50, Robert Dewar wrote:
>> [..]
>>
>> I actually disagree with this, I think attempting to make the link fail
>> here would be a mistake.
Why do you think that this would be a mistake?
WR
Hello Michael,
On Thu Oct 06, 2005 15:54, Michael Veksler wrote:
[..]
>> 2. I think that it will break C. As I remember, it is sometimes
>> legal in C (or in some dialects of C) to have conflicting types.
>> You may define in one translation unit:
>> char var[5];
>> and the
merged into the mainline.". Without "preceding" or "following",
or at least leading dash or a trailing colon, I'm at a loss whether that
refers to the branches named before or after.
(The somewhat formal address contributed to landing this message
in the SPAM p
config.guess:
i686-pc-linux-gnu
gcc --v:
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ./configure
Thread model: posix
gcc version 4.4.3 (GCC)
packages:
gcc-4.4.3.tar.bz2
gcc-core-4.4.3.tar.bz2
gcc-g++-4.4.3.tar.bz2
linux distribution:
Ubuntu 8.04.4 LTS \n \l
kernel version:
b and step through the code, etc.
When I type the suggested command, I get
(gdb) p browse_tree (current_function_decl)
No symbol "browse_tree" in current context.
(gdb)
What i'm doing wrong? Any ideas?
Thanks,
Wolfgang
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetz
found arm.md and the moveqi insns, but because of the different
addressing modes of strb and swpb, its not easy to make the change.
And there must be a compiler option for this, too.
Could somebody please tell me how to implement this change?
regards
Wolfgang
--
We're back to the times when men
d additional reload-related machinery.
>
> I suspect it would be better to make GCC do halfword stores instead
> (read/modify/write).
Hmmm... I have thought about that. But how do the compiler know if the
byte address is even or odd? Every time testing the LSB of the address
and making co
>|| register_operand (operands[1], QImode))"
>
> "@
>mov%?\\t%0, %1
>mvn%?\\t%0, #%B1
> ldr%?b\\t%0, %1
>swp%?b\\t%1, %1, [%M0]"
> [(set_attr "type" "*,*,load1,store1")
>(set_attr "predicable" "yes")]
> )
Changing "m" to "Q", narrowing the address modes
Changing "r" to "+r", (register is globbered)
and of course making the swpb call..
Gcc compiles, but does a segfault while compiling ARM programs.
regards
Wolfgang
--
We're back to the times when men were men
and wrote their own device drivers.
(Linus Torvalds)
h:QI 2 "=X,X,X,1"))]
"TARGET_ARM
&& ( register_operand (operands[0], QImode)
|| register_operand (operands[1], QImode))"
"@
mov%?\\t%0, %1
mvn%?\\t%0, #%B1
ldr%?b\\t%0, %1
str%?b\\t%1, %0"
[(set_attr "type" "*,*,load1,store1")
of the
swpb instruction.
And then I can recode the
(define_expand "movqi"
[(set (match_operand:QI 0 "general_operand" "")
(match_operand:QI 1 "general_operand" ""))]
to cope with the movqi requirements defined in the gcc manual.
Hmmm... wondering who all these xxx_operand functions are defined, and
where they are documented...
Is this the right way to go?
regards
Wolfgang
--
We're back to the times when men were men
and wrote their own device drivers.
(Linus Torvalds)
Paul,
On Sunday 04 June 2006 13:24, Paul Brook wrote:
> On Sunday 04 June 2006 11:31, Wolfgang Mües wrote:
> > Splitting the insn
> >
> > (define_insn "*arm_movqi_insn"
> > [(set (match_operand:QI 0 "nonimmediate_operand" "=r,r,r,m"
n of code to understand what's going on
there.
Thanks, Paul.
regards
Wolfgang
--
We're back to the times when men were men
and wrote their own device drivers.
(Linus Torvalds)
ssues now. Compiler comes first.
We will need an asm macro for 8bit writes to the hardware registers.
And the devkitARM libraries *must* implement writeback caching for the
GBA slot ROM area.
regards
Wolfgang
--
We're back to the times when men were men
and wrote their own device drivers.
(Linus Torvalds)
implemented before, it was 100 times slower than
native access. Unusable.
regards
Wolfgang
--
We're back to the times when men were men
and wrote their own device drivers.
(Linus Torvalds)
, #0]" was coded before, because the
assembler understands "[%r]" very well for all instructions. The form
"[%r]" has a wider usage because it covers swp too.
On Sunday 04 June 2006 23:36, Rask Ingemann Lambertsen wrote:
> On Wed, May 31, 2006 at 10:49:35PM +0200, Wolfgang Müe
Rask,
On Monday 05 June 2006 16:16, Rask Ingemann Lambertsen wrote:
> On Mon, Jun 05, 2006 at 01:47:10PM +0200, Wolfgang Mües wrote:
> Does GCC happen to accept "[%r, #0]" for swp?
No. But no problem here to change that.
> I think the comment in arm.h is wrong. The manual
dup 0) (match_dup 1))
> (clobber (match_dup 1))]
> )]
> )
I will try this.
> Yet another register which stands a good chance of being reusable is
> the register containing the address.
Yes, but that is not allowed according to the specification of the swp
instruction. The add
to swpb. The non-working 'Q' constraint
regards
Wolfgang
--
We're back to the times when men were men
and wrote their own device drivers.
(Linus Torvalds)
in fs/vfat/namei.c I get:
> fs/vfat/namei.c: In function 'vfat_add_entry':
> fs/vfat/namei.c:694: error: unrecognizable insn:
> (insn 2339 2338 2340 188 (set (mem/s/j:QI (reg:SI 14 lr) [0
> .attr+0 S1 A8]) (reg:QI 12 ip)) -1 (nil)
> (nil))
> fs/vfat/namei.c:694:
much places with
> emit_constant_insn (cond,
> gen_rtx_SET (VOIDmode, target, source));
Isn't it better to replace gen_rtx_SET?
regards
Wolfgang
--
We're back to the times when men were men
and wrote their own device drivers.
(Linus Torvalds)
byte into a struct member referenced by a pointer) is not
evaluated.
I fear that these problems are creating an endless story, and sorry for
generating traffic on this list, because I'm still no gcc expert...
On the other hand, the compiler now has generated code from hundreds of
files, and maybe I'm very near to success now.
regards
Wolfgang
--
We're back to the times when men were men
and wrote their own device drivers.
(Linus Torvalds)
works.
Yes, it works. Kernel and userland are compiling now. I can't find any
errors in the generated code. Many thanks!
regards
Wolfgang
--
We're back to the times when men were men
and wrote their own device drivers.
(Linus Torvalds)
1 "../../svn-mainline/gcc/c-lang.c"
# 23 "../../svn-mainline/gcc/c-lang.c"
# 1 "./config.h" 1 3
# 1 "./auto-host.h" 1 3
This must be something that someone has seen before and knows how to deal
eep up the good work!
Wolfgang Mües
ting system and hardware). So, every System z machine uses code
generated by gcc, even if there if the system does not yet run Linux.
Regards, Wolfgang
ias in its preconditions but alias information is not generated due to
the second option.
Regards, Wolfgang
---
Dr. Wolfgang Gellerich
IBM Deutschland Entwicklung GmbH
Schönaicher Strasse 220
71032 Böblingen, Germany
Tel. +49 / 7031 / 162598
[EMAIL PROTECTED]
===
IBM D
> On 10/10/07, Wolfgang Gellerich <[EMAIL PROTECTED]> wrote:
> >
> > There is a conflict between the command line switches that turn
> off individual
> > optimization steps and their preconditions. Compiling a "hello
> world" with the
> > foll
I'm seeing a boostrap failure when I try to build the latest gcc version
( 8833eab4461b4b7050f06a231c3311cc1fa87523 ) :
checking whether time.h and sys/time.h may both be included... checking
whether
gcc supports -Wmissing-prototypes... i686-pc-linux-gnu
checking host system type... make[3]: *** [
On 20/03/15 16:02, Claudiu Zissulescu wrote:
Hi Joern,
I have a small patch for ARC backend that fixes the value of instruction length
attribute when the instruction is predicated. Ok to apply?
Why would the arc_bdr_iscond test have any effect?
arc_predicate_delay_insns should render the iss
On 20/03/15 16:02, Claudiu Zissulescu wrote:
Hi Joern,
I have a small patch for ARC backend that fixes the value of instruction length
attribute when the instruction is predicated. Ok to apply?
Assuming you tested it, this patch is OK.
I want to submit some vectorizer patches, what would be a suitable
regression test?
Preferably some native or cross test that can run on an i7 x86_64
GNU/Linux machine.
To give an idea what code I'm patching, here are the patches I got so far:
* tree-vect-patterns.c (vect_recog_dot_pro
On 30/10/18 08:36, Richard Biener wrote:
On Mon, Oct 29, 2018 at 7:03 PM Joern Wolfgang Rennecke
wrote:
I want to submit some vectorizer patches, what would be a suitable
regression test?
I am sure you have testcases, no? For new features please make them
dg-do run ones by checking
We've been running builds/regression tests for GCC 8.2 configured with
--enable-checking=all, and have observed some failures related to
garbage collection.
First problem:
The g++.dg/pr85039-2.C tests (I've looked in detail at -std=c++98, but
-std=c++11 and -std=c++14 appear to follow the sam
d __GNUC__ */
But I do not know if this fix may break stuff in some places.
Another restart of make yields a full build and I am able to install the
compiler and use it. it seems to generate proper result (at least for C).
In case you have further questions, do not hesitate to contact me via e
The tsvc tests take just too long on simulators, particularly if there
is little or no vectorization of the test because of compiler
limitations, target limitations, or the chosen options. Having
151 tests time out at a quarter of an hour is not fun, and making the
time out go away by upping th
While on x86_64-pc-linux-gnu, the second diagram shows the type written
as 'int', as expected, on a 16 and 32 bit newlib based toolchain, it is
being output as int32_t . And all the formatting is also a bit
different, probably due to the change in how the int32_t is displayed.
What do other p
On 22/07/2024 16:44, David Malcolm wrote:
Does it help to hack this change into prune.exp:
diff --git a/gcc/testsuite/lib/prune.exp b/gcc/testsuite/lib/prune.exp
index d00d37f015f7..f467d1a97bc6 100644
--- a/gcc/testsuite/lib/prune.exp
+++ b/gcc/testsuite/lib/prune.exp
@@ -109,7 +109,7 @@ proc
On 22/07/2024 17:13, Joern Wolfgang Rennecke wrote:
> I guess you could reduce the differences between platforms if you
didn't
use types as defined by headerfiles directly, as they might be #defines
or typedefs or whatever, and instead used your own typedef or struct types.
It
52 matches
Mail list logo
