[Bug c/38295] Support pointer difference as constant in static initializer

2016-10-12 Thread fw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38295 --- Comment #11 from Florian Weimer --- Created attachment 39799 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39799&action=edit label.c (In reply to Andrew Pinski from comment #6) > Not always since they could be in different sections vi

[Bug c/38295] Support pointer difference as constant in static initializer

2016-10-07 Thread fw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38295 Florian Weimer changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED CC|

[Bug c/38295] Support pointer difference as constant in static initializer

2016-04-15 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38295 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug c/38295] Support pointer difference as constant in static initializer

2008-11-27 Thread gnu at behdad dot org
--- Comment #8 from gnu at behdad dot org 2008-11-27 18:55 --- If they are asked to be put in different sections, sure, it will err. But doesn't gcc already use relative calls for many static functions in the same unit? Let me back out: my request is: add gcc extension to support some

[Bug c/38295] Support pointer difference as constant in static initializer

2008-11-27 Thread pinskia at gcc dot gnu dot org
--- Comment #7 from pinskia at gcc dot gnu dot org 2008-11-27 18:53 --- Also the linker could do some branch relaxation which causes the size to be different based on the layout of the functions. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38295

[Bug c/38295] Support pointer difference as constant in static initializer

2008-11-27 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2008-11-27 18:52 --- (In reply to comment #5) > If the two functions are in the same compilation unit (and static), it's known > at compile time, isn't it? Not always since they could be in different sections via -ffunction-sections or

[Bug c/38295] Support pointer difference as constant in static initializer

2008-11-27 Thread gnu at behdad dot org
--- Comment #5 from gnu at behdad dot org 2008-11-27 18:35 --- If the two functions are in the same compilation unit (and static), it's known at compile time, isn't it? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38295

[Bug c/38295] Support pointer difference as constant in static initializer

2008-11-27 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2008-11-27 18:33 --- (In reply to comment #2) > I'm not following. Why arrays? Those are pointers, and their difference is > known at compile time. Not at compile time really, the difference is known at link time. -- http://gcc.

[Bug c/38295] Support pointer difference as constant in static initializer

2008-11-27 Thread gnu at behdad dot org
--- Comment #3 from gnu at behdad dot org 2008-11-27 18:32 --- Oh, I see what you mean. Yes, I said in my report that this is undefined/unsupported/... according to the C standard. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38295

[Bug c/38295] Support pointer difference as constant in static initializer

2008-11-27 Thread gnu at behdad dot org
--- Comment #2 from gnu at behdad dot org 2008-11-27 18:31 --- I'm not following. Why arrays? Those are pointers, and their difference is known at compile time. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38295

[Bug c/38295] Support pointer difference as constant in static initializer

2008-11-27 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-11-27 18:28 --- Differences between two different arrays don't make sense really. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38295