https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94134
--- Comment #17 from Stephen Casner ---
Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94835
Stephen Casner changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94835
--- Comment #4 from Stephen Casner ---
I verified that the compilation of chrono:544 is the first time in the build
that the failing assert is executed, so that likely implies that the problem is
general and not specific to the particular source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94835
--- Comment #3 from Stephen Casner ---
I'm working with unmodified gcc sources, but if no other targets are seeing
this problem then it may be caused by pdp11-specific code somewhere else. I
guess that g++ and libstdc++v3 have never been success
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94835
--- Comment #2 from Stephen Casner ---
Created attachment 48400
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48400&action=edit
log of compilation with -v
(Not sure why the initial attachment was deleted.)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94835
--- Comment #1 from Stephen Casner ---
Created attachment 48398
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48398&action=edit
preprocessed source chrono.ii
++
Assignee: unassigned at gcc dot gnu.org
Reporter: casner at acm dot org
Target Milestone: ---
I am working on a pdp11-elf32 target in binutils with the goal of being able to
compile C++ for the PDP11 (an effort instigated by Paul Koning, gcc PDP11
maintainer). I have a first
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94134
--- Comment #13 from Stephen Casner ---
(In reply to Stephen Casner from comment #9)
(Commenting on my own comment)
> 1. pdp11-aout does not have a .lcommon or .lcomm section, just .text, .data
> and .bss. But also I'm missing something about th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94134
--- Comment #12 from Stephen Casner ---
(In reply to pkoning from comment #11)
> (In reply to Stephen Casner from comment #9)
> > 7. Emitting the zero-initialized variable into .data when it happens to
> > follow a nonzero-initialized variable is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94134
--- Comment #10 from Stephen Casner ---
One more question: I'm working on binutils ld as well, wanting to implement a
new option --imagic for pdp11-aout that outputs magic number 0413 and sets both
.text and .data at address 0 (with .bss to foll
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94134
--- Comment #9 from Stephen Casner ---
Thank you all for your prompt action on this bug. I have some comments and
questions if you are willing to help with my education about gcc internals:
1. pdp11-aout does not have a .lcommon or .lcomm secti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94085
--- Comment #1 from Stephen Casner ---
Please mark this bug RESOLVED DUPLICATE of bug 94134.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94134
Stephen Casner changed:
What|Removed |Added
Target||pdp11-aout
--- Comment #1 from Stephen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94085
Stephen Casner changed:
What|Removed |Added
CC||casner at acm dot org
This bug lost
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: casner at acm dot org
Target Milestone: ---
The assembler output for a C program compiled for the pdp11-aout target begins
with a .text directive. If that program begins with a
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: casner at acm dot org
Target Milestone: ---
The assembler output for a C program compiled for the pdp11-aout target begins
with a .text directive. If that program begins with a
16 matches
Mail list logo
