https://gcc.gnu.org/g:0f9752e4b23cab42709824ca8f504b0dcd941c10
commit 0f9752e4b23cab42709824ca8f504b0dcd941c10
Author: Pierre-Emmanuel Patry
Date: Mon Nov 20 11:37:12 2023 +0100
Add a test regular variadic functions errors
Add a new regression test for the error message
https://gcc.gnu.org/g:afb8e75e08526cdde7a513a56050046dc0ba0368
commit afb8e75e08526cdde7a513a56050046dc0ba0368
Author: Pierre-Emmanuel Patry
Date: Wed Oct 18 14:31:53 2023 +0200
Parse variadic functions
Variadic functions were not parsed because it is an unstable feature
From: Pierre-Emmanuel Patry
Add a new regression test for the error message in regular function
variadic errors during ast validation pass.
gcc/testsuite/ChangeLog:
* rust/compile/non_foreign_variadic_function.rs: New test.
Signed-off-by: Pierre-Emmanuel Patry
---
From: Pierre-Emmanuel Patry
Add a new regression test for the error message in regular function
variadic errors during ast validation pass.
gcc/testsuite/ChangeLog:
* rust/compile/non_foreign_variadic_function.rs: New test.
Signed-off-by: Pierre-Emmanuel Patry
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79364
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |8.0
Status|UNCONFIRMED
On Thu, 20 Oct 2022, Richard Biener via Gcc wrote:
> > 1. How should (...) be represented differently from unprototyped functions
> > so that stdarg_p and prototype_p handle it properly? Should I add a new
> > language-independent type flag (there are plenty spare) to use for this?
>
> I'd say
On Thu, Oct 20, 2022 at 1:54 AM Joseph Myers wrote:
>
> C2x allows variable-argument functions declared with (...) as parameters -
> no named arguments - as in C++. It *also* allows such functions to access
> their parameters, unlike C++, by relaxing the requirements on va_start so
> it no
C2x allows variable-argument functions declared with (...) as parameters -
no named arguments - as in C++. It *also* allows such functions to access
their parameters, unlike C++, by relaxing the requirements on va_start so
it no longer needs to be passed the name of the last named parameter.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103810
--- Comment #2 from Eric Gallager ---
(In reply to jos...@codesourcery.com from comment #1)
> Note also that there is a proposal for C23 (N2854) to allow such
> functions, including changing the requirements on va_start to make it
> possible
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103810
--- Comment #1 from joseph at codesourcery dot com ---
Note also that there is a proposal for C23 (N2854) to allow such
functions, including changing the requirements on va_start to make it
possible to read their arguments.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103810
Bug ID: 103810
Summary: -fallow-parameterless-variadic-functions flag could
use a testcase that covers its documentation better
Product: gcc
Version: 12.0
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79364
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79364
--- Comment #4 from Guillaume Knispel ---
The dup seems to be 69846
This might also be vaguely related to 52154
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79364
Richard Biener changed:
What|Removed |Added
Keywords||ABI
--- Comment #3 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79364
--- Comment #2 from Guillaume Knispel ---
Note: I hit that bug after cleaning some real code after a cppcheck static
analysis. The original code sometimes had "..." after references, which is
technically forbidden (but seems to work with g++,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79364
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
--- Comment #1 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79364
Bug ID: 79364
Summary: some variadic functions miscompiled (at least for x64
targets)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
This one fixes support for D-style variadic functions, specifically
where non-variadic parameters can be omitted entirely.
Iain
---
libiberty/
2016-01-26 Iain Buclaw <ibuc...@gdcproject.org>
* d-demangle.c (dlang_function_args): Append ',' for variadic functions
only if parameter
On Tue, Jan 26, 2016 at 4:36 PM, Iain Buclaw <ibuc...@gdcproject.org> wrote:
> This one fixes support for D-style variadic functions, specifically
> where non-variadic parameters can be omitted entirely.
This is OK.
Thanks.
Ian
Joseph, is this what you had in mind in this PR? With this patch, we
warn anytime we see a prototype-less function that is variadic. It
seems rare enough not to warrant a separate warning option for it.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2015-10-21 Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68024
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On Wed, 21 Oct 2015, Marek Polacek wrote:
> Joseph, is this what you had in mind in this PR? With this patch, we
> warn anytime we see a prototype-less function that is variadic. It
> seems rare enough not to warrant a separate warning option for it.
>
> Bootstrapped/regtested on x86_64-linux,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68024
--- Comment #2 from Marek Polacek ---
Author: mpolacek
Date: Wed Oct 21 17:30:20 2015
New Revision: 229131
URL: https://gcc.gnu.org/viewcvs?rev=229131=gcc=rev
Log:
PR c/68024
* c-decl.c (start_function): Warn about vararg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68024
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68024
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68024
Bug ID: 68024
Summary: Diagnose variadic functions defined without prototypes
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61898
--- Comment #4 from Andi Kleen andi-gcc at firstfloor dot org ---
The patch has several issues (making it currently fail bootstrap):
- it warns for vfprintf too (fixed)
- on i386 it gets confused between va_list * and char *, so something like
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61898
Andi Kleen andi-gcc at firstfloor dot org changed:
What|Removed |Added
CC||andi-gcc at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61898
--- Comment #1 from ak at gcc dot gnu.org ---
I agree such a warning would make sense.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61898
Manuel López-Ibáñez manu at gcc dot gnu.org changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61898
Bug ID: 61898
Summary: Variadic functions accept va_list without warning
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
Hi All,
In our private port ,we define function_arg hook to pass the first
three args in the reg and rest will go to stack.
But for variadic functions the arguments need to pass through the stack.
How we can achieve this ?? Any inputs will be appreciate.
Thank you
~Umesh
On Fri, Apr 25, 2014 at 11:27 AM, Umesh Kalappa
umesh.kalap...@gmail.com wrote:
In our private port ,we define function_arg hook to pass the first
three args in the reg and rest will go to stack.
But for variadic functions the arguments need to pass through the stack.
How we can
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47025
Richard Guenther rguenth at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47025
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
CC||jakub at gcc dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47025
--- Comment #5 from Richard Guenther rguenth at gcc dot gnu.org 2011-09-06
15:56:26 UTC ---
Author: rguenth
Date: Tue Sep 6 15:56:20 2011
New Revision: 178601
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=178601
Log:
2011-09-06 Richard
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47025
Richard Guenther rguenth at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48731
--- Comment #2 from Richard Guenther rguenth at gcc dot gnu.org 2011-04-26
12:59:33 UTC ---
Author: rguenth
Date: Tue Apr 26 12:59:22 2011
New Revision: 172963
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=172963
Log:
2011-04-26 Richard
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48731
--- Comment #3 from Richard Guenther rguenth at gcc dot gnu.org 2011-04-26
13:00:58 UTC ---
Author: rguenth
Date: Tue Apr 26 13:00:53 2011
New Revision: 172964
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=172964
Log:
2011-04-26 Richard
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48731
Richard Guenther rguenth at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48731
Richard Guenther rguenth at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48731
Summary: regression: __attribute__((flatten)) produces error
with function calling variadic functions
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
: Variadic functions
Date: Tue, 08 Jun 2010 09:22:28 +0200
Hi,
I am working on the OPENRISC32 (or32) architecture port of uClibc and
have run into a bit of conundrum that I was hoping someone could help me
understand a bit better. Please bear with me...
--
The preconditions:
i
behaviour in C/C++. The standard does not guarantee that
this program will work.
i) Is my compiler broken? If so, is there somewhere in GCC that
specifically handles register/stack parameter passing for variadic
functions??? (GCC 4.2, patched for or32)
This problem does not indicate that your
--- Comment #4 from jason at gcc dot gnu dot org 2008-11-14 23:18 ---
Fixed.
--
jason at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSIGNED
--- Comment #3 from jan dot kratochvil at redhat dot com 2008-10-07 23:10
---
FYI I find at least this specific reported testcase as already fixed by Jason:
http://gcc.gnu.org/ml/gcc-patches/2008-09/msg00729.html
http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00189.html
GCC now even
--- Comment #2 from paolo dot carlini at oracle dot com 2008-10-03 10:51
---
Then, I guess we can just assign to Jason.
--
paolo dot carlini at oracle dot com changed:
What|Removed |Added
);
}
_Z3fooIiiEiT_T1_
--
Summary: Demangling of variadic functions
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Keywords: ABI
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc
--- Comment #1 from jason at redhat dot com 2008-10-03 02:27 ---
Subject: Re: New: Demangling of variadic functions
I've been working on a bunch of mangling/demangling issues lately, this
among them.
Jason
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37718
-temps a.c
--
Summary: long long bit fields are passed to variadic functions as
longs
Product: gcc
Version: 3.2.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo
--- Comment #1 from bugzilla at hburch dot com 2006-03-29 14:54 ---
Created an attachment (id=11150)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11150action=view)
Bundle for Linux
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26921
--- Comment #2 from bugzilla at hburch dot com 2006-03-29 14:54 ---
Created an attachment (id=11151)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11151action=view)
Bundle for Mac OS X
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26921
--- Comment #3 from bugzilla at hburch dot com 2006-03-29 14:59 ---
#include stdio.h
struct s {
long long int a : 33;
};
struct s foo = {0};
int main(void) {
printf (%lld\n, foo.a);
return 0;
}
produces the following output using gcc -Wall -o a a.c for same
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-03-29 19:25 ---
The warning mess has been corrected:
t.c: In function 'main':
t.c:10: warning: format '%lld' expects type 'long long int', but argument 2 has
type 'long long int:33'
This is not a bug, GCC is correct in warning.
--- Additional Comments From bonzini at gnu dot org 2004-06-15 15:26 ---
Graham is right. This is a problem in user code, unless this fails as well...
int variadic_test (int, unsigned long, unsigned long);
int main (void)
{
int result_varfunc;
int result_local;
55 matches
Mail list logo
