test.c
```
void my_fun(int *arr, int N)
{
int sum = 0;
for (int i = 0; i < N; ++i) {
sum += arr[i];
}
}
int main(void)
{
return 0;
}
```
clang -c -g test.c ; objdump -S test.o > test.s
`my_fun` appears twice in the disassembly code.
Excerpt of test.s:
```
void my_fun(int *
https://sourceware.org/bugzilla/show_bug.cgi?id=18452
Alan Modra changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=19921
--- Comment #3 from Jamey Hicks ---
Created attachment 9170
--> https://sourceware.org/bugzilla/attachment.cgi?id=9170&action=edit
patch adding --verilog-data-width option to objcopy
This patch adds --verilog-data-width option to objcopy. I
https://sourceware.org/bugzilla/show_bug.cgi?id=18452
--- Comment #17 from cvs-commit at gcc dot gnu.org ---
The master branch has been updated by Alan Modra :
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=136a43b762ce7bc692645cc0d9d50c934f9aa392
commit 136a43b762ce7bc692645cc0d9d5
https://sourceware.org/bugzilla/show_bug.cgi?id=19921
--- Comment #2 from Jamey Hicks ---
After talking about it with others who use the verilog output, a new option
seems best because it is the most flexible. The data width of a ROM does not
necessarily match the data width of the processor.
I
https://sourceware.org/bugzilla/show_bug.cgi?id=19921
Nick Clifton changed:
What|Removed |Added
CC||nickc at redhat dot com
--- Comment #1
https://sourceware.org/bugzilla/show_bug.cgi?id=19910
--- Comment #14 from Nick Clifton ---
Hi Alan,
> sparc-aout +FAIL: PR19910 - make sure that U suffix is accepted
> sparc-coff +FAIL: PR19910 - make sure that U suffix is accepted
Are we still supporting those targets ? I had no idea. :-)
https://sourceware.org/bugzilla/show_bug.cgi?id=19910
--- Comment #13 from cvs-commit at gcc dot gnu.org ---
The master branch has been updated by Nick Clifton :
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=992dc2c47069220ce5a94829a8d8fed3ee72a1d0
commit 992dc2c47069220ce5a94829a8
