* [Bug tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
2024-06-27 10:45 [Bug tree-optimization/115679] New: inlining failed in call to 'foo': function not considered for inlining Changqing.Li at windriver dot com
@ 2024-06-27 12:32 ` rguenth at gcc dot gnu.org
2024-06-27 13:38 ` hubicka at ucw dot cz
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: rguenth at gcc dot gnu.org @ 2024-06-27 12:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115679
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
With -Og it's usually that the always-inline function is called indirectly -
that's an unsupported case.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
2024-06-27 10:45 [Bug tree-optimization/115679] New: inlining failed in call to 'foo': function not considered for inlining Changqing.Li at windriver dot com
2024-06-27 12:32 ` [Bug tree-optimization/115679] " rguenth at gcc dot gnu.org
@ 2024-06-27 13:38 ` hubicka at ucw dot cz
2024-06-27 19:40 ` pinskia at gcc dot gnu.org
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: hubicka at ucw dot cz @ 2024-06-27 13:38 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115679
--- Comment #2 from Jan Hubicka <hubicka at ucw dot cz> ---
> With -Og it's usually that the always-inline function is called indirectly -
> that's an unsupported case.
We can probably add CIF code for functions that were called indirectly
but are no more, so this is reported better. I will cook up patch.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
2024-06-27 10:45 [Bug tree-optimization/115679] New: inlining failed in call to 'foo': function not considered for inlining Changqing.Li at windriver dot com
2024-06-27 12:32 ` [Bug tree-optimization/115679] " rguenth at gcc dot gnu.org
2024-06-27 13:38 ` hubicka at ucw dot cz
@ 2024-06-27 19:40 ` pinskia at gcc dot gnu.org
2024-07-03 0:57 ` Changqing.Li at windriver dot com
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-06-27 19:40 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115679
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2024-06-27
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Can you provide the preprocessed source?
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
2024-06-27 10:45 [Bug tree-optimization/115679] New: inlining failed in call to 'foo': function not considered for inlining Changqing.Li at windriver dot com
` (2 preceding siblings ...)
2024-06-27 19:40 ` pinskia at gcc dot gnu.org
@ 2024-07-03 0:57 ` Changqing.Li at windriver dot com
2024-07-03 0:59 ` Changqing.Li at windriver dot com
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Changqing.Li at windriver dot com @ 2024-07-03 0:57 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115679
--- Comment #4 from Li, Changqing <Changqing.Li at windriver dot com> ---
Created attachment 58570
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58570&action=edit
preprocessed source
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
2024-06-27 10:45 [Bug tree-optimization/115679] New: inlining failed in call to 'foo': function not considered for inlining Changqing.Li at windriver dot com
` (3 preceding siblings ...)
2024-07-03 0:57 ` Changqing.Li at windriver dot com
@ 2024-07-03 0:59 ` Changqing.Li at windriver dot com
2024-07-03 1:05 ` pinskia at gcc dot gnu.org
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Changqing.Li at windriver dot com @ 2024-07-03 0:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115679
--- Comment #5 from Li, Changqing <Changqing.Li at windriver dot com> ---
Hi,
I have attached the preprocessed source. You can also get it from here:
https://cairographics.org/releases/pixman-0.43.4.tar.gz
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
2024-06-27 10:45 [Bug tree-optimization/115679] New: inlining failed in call to 'foo': function not considered for inlining Changqing.Li at windriver dot com
` (4 preceding siblings ...)
2024-07-03 0:59 ` Changqing.Li at windriver dot com
@ 2024-07-03 1:05 ` pinskia at gcc dot gnu.org
2024-07-03 1:19 ` Changqing.Li at windriver dot com
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-07-03 1:05 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115679
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Li, Changqing from comment #4)
> Created attachment 58570 [details]
> preprocessed source
This is not the preprocessed source.
Please read https://gcc.gnu.org/bugs/ and try again.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
2024-06-27 10:45 [Bug tree-optimization/115679] New: inlining failed in call to 'foo': function not considered for inlining Changqing.Li at windriver dot com
` (5 preceding siblings ...)
2024-07-03 1:05 ` pinskia at gcc dot gnu.org
@ 2024-07-03 1:19 ` Changqing.Li at windriver dot com
2024-07-03 4:52 ` pinskia at gcc dot gnu.org
2024-07-03 4:58 ` pinskia at gcc dot gnu.org
8 siblings, 0 replies; 10+ messages in thread
From: Changqing.Li at windriver dot com @ 2024-07-03 1:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115679
Li, Changqing <Changqing.Li at windriver dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #58570|0 |1
is obsolete| |
--- Comment #7 from Li, Changqing <Changqing.Li at windriver dot com> ---
Created attachment 58571
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58571&action=edit
pixman-combine-float.c.i
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
2024-06-27 10:45 [Bug tree-optimization/115679] New: inlining failed in call to 'foo': function not considered for inlining Changqing.Li at windriver dot com
` (6 preceding siblings ...)
2024-07-03 1:19 ` Changqing.Li at windriver dot com
@ 2024-07-03 4:52 ` pinskia at gcc dot gnu.org
2024-07-03 4:58 ` pinskia at gcc dot gnu.org
8 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-07-03 4:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115679
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #2)
> > With -Og it's usually that the always-inline function is called indirectly -
> > that's an unsupported case.
> We can probably add CIF code for functions that were called indirectly
> but are no more, so this is reported better. I will cook up patch.
Yes it is indirect function call.
So yes this is invalid at -Og.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
2024-06-27 10:45 [Bug tree-optimization/115679] New: inlining failed in call to 'foo': function not considered for inlining Changqing.Li at windriver dot com
` (7 preceding siblings ...)
2024-07-03 4:52 ` pinskia at gcc dot gnu.org
@ 2024-07-03 4:58 ` pinskia at gcc dot gnu.org
8 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-07-03 4:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115679
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
static __inline__ __attribute__ ((__always_inline__)) void
combine_inner (pixman_bool_t component,
float *dest, const float *src, const float *mask, int n_pixels,
combine_channel_t combine_a, combine_channel_t combine_c)
{
...
combine_c(...)
static float __inline__ __attribute__ ((__always_inline__)) pd_combine_clear
(float sa, float s, float da, float d) { const float fa = get_factor (ZERO, sa,
da); const float fb = get_factor (ZERO, sa, da); return ((1.0f < s * fa + d *
fb) ? 1.0f : s * fa + d * fb); }
...
static void combine_clear_ca_float (pixman_implementation_t *imp, pixman_op_t
op, float *dest, const float *src, const float *mask, int n_pixels) {
combine_inner (1, dest, src, mask, n_pixels, pd_combine_clear,
pd_combine_clear); }
*** This bug has been marked as a duplicate of bug 107931 ***
^ permalink raw reply [flat|nested] 10+ messages in thread