在 2022/11/25 15:48, Dave Blanchard 写道:
While I sympathize with the desire to get rid of crud (and I agree that AT&T
syntax is crud), as stated above it wouldn't really make a practical difference.
For distro maintainers it would likely break some/many older packages which assumed
the old defau
On Fri, 25 Nov 2022, LIU Hao via Gcc wrote:
I am a Windows developer and I have been writing x86 and amd64 assembly for
more than ten years. One annoying thing about GCC is that, for x86 if I need
to write I piece of inline assembly then I have to do it twice: one in AT&T
syntax and one in Int
在 2022/11/25 16:50, Marc Glisse 写道:
On Fri, 25 Nov 2022, LIU Hao via Gcc wrote:
I am a Windows developer and I have been writing x86 and amd64 assembly for more than ten years.
One annoying thing about GCC is that, for x86 if I need to write I piece of inline assembly then I
have to do it twic
On Fri, 25 Nov 2022 at 09:16, LIU Hao via Gcc wrote:
>
> 在 2022/11/25 16:50, Marc Glisse 写道:
> > On Fri, 25 Nov 2022, LIU Hao via Gcc wrote:
> >
> >> I am a Windows developer and I have been writing x86 and amd64 assembly
> >> for more than ten years.
> >> One annoying thing about GCC is that, fo
On Fri, Nov 25, 2022 at 02:39:41PM +0800, LIU Hao via Gcc wrote:
> I am a Windows developer and I have been writing x86 and amd64 assembly for
> more than ten years. One annoying thing about GCC is that, for x86 if I need
> to write I piece of inline assembly then I have to do it twice: one in AT&T
Awesome method just for you https://bit.ly/3ADHsha
With gratitude,William Loan Firm
> On 25 Nov 2022, at 09:11, LIU Hao via Gcc wrote:
>
> 在 2022/11/25 16:50, Marc Glisse 写道:
>> On Fri, 25 Nov 2022, LIU Hao via Gcc wrote:
>>> I am a Windows developer and I have been writing x86 and amd64 assembly for
>>> more than ten years. One annoying thing about GCC is that, for x86 if I
Hello!
On Mac OS X/macOS configure scripts leave conftest.dSYM subdirectories behind,
created by dsymutil:
checking for build system preprocessor... rm: conftest.dSYM: is a
directory
checking for build system executable suffix... rm: conftest.dSYM: is a
directory
checki
在 2022/11/25 17:32, Jakub Jelinek 写道:
So just use -masm=intel yourself and don't force it on others.
Other people are familiar with AT&T syntax rather than Intel syntax,
in fact, as history shows, Intel syntax is a second class citizen that often
takes years to fix up for new instructions. The
On Fri, Nov 25, 2022 at 1:03 PM LIU Hao via Gcc wrote:
>
> 在 2022/11/25 17:32, Jakub Jelinek 写道:
> > So just use -masm=intel yourself and don't force it on others.
> >
> > Other people are familiar with AT&T syntax rather than Intel syntax,
> > in fact, as history shows, Intel syntax is a second c
On 25/11/2022 07:39, LIU Hao via Gcc wrote:
I am a Windows developer and I have been writing x86 and amd64 assembly
for more than ten years. One annoying thing about GCC is that, for x86
if I need to write I piece of inline assembly then I have to do it
twice: one in AT&T syntax and one in Inte
Hi Pete,
> On 25 Nov 2022, at 10:36, Peter Dyballa via Gcc wrote:
> On Mac OS X/macOS configure scripts leave conftest.dSYM subdirectories
> behind, created by dsymutil:
>
> checking for build system preprocessor... rm: conftest.dSYM: is a
> directory
> checking for build system e
On 11/16/22 10:01, tao.z...@amlogic.com wrote:
> Dear gcc:
>
Hello.
Based on quick discussion with Jakub, we believe fasan-shadow-symbol= would
be a non-trivial amount of work
and we rather suggest doing a per-system build with investigated
-fasan-shadow-offset.
Cheers,
Martin
> I am
On Wed, 2022-11-23 at 20:49 -0500, Gavin Ray via Gcc wrote:
> Hey all, just a few questions about the fantastic GCC Static
> Analyzer:
Hi!
>
> - It's stated that support for C++ vs C is very limited. Does this
> apply if
> you're writing C++ that is very similar-looking to C and uses few
> of
> Unfortunately not: even fairly simple-looking C++ code can generate extra CFG
edges relating to exception-handling ... making the output essentially useless.
Ahh, I had figured the answer might be something like this. Thanks for
confirming. At least from the small codebase I have, swapping from
I'm trying to use fairly recent GCC sources (the gcc-darwin branch to be
precise) to build Ada, starting with the latest (2020) release of Gnat from
Adacore.
It fails for several reasons. One is that two source files use [ ] for array
initializer brackets when ( ) is apparently supposed to be
On Fri, Nov 25, 2022 at 11:59 AM Paul Koning via Gcc wrote:
>
> I'm trying to use fairly recent GCC sources (the gcc-darwin branch to be
> precise) to build Ada, starting with the latest (2020) release of Gnat from
> Adacore.
Are you building a cross compiler or a native compiler?
If you are bu
> On Nov 25, 2022, at 3:03 PM, Andrew Pinski wrote:
>
> On Fri, Nov 25, 2022 at 11:59 AM Paul Koning via Gcc wrote:
>>
>> I'm trying to use fairly recent GCC sources (the gcc-darwin branch to be
>> precise) to build Ada, starting with the latest (2020) release of Gnat from
>> Adacore.
>
>
On Fri, Nov 25, 2022 at 12:08 PM Paul Koning wrote:
>
>
>
> > On Nov 25, 2022, at 3:03 PM, Andrew Pinski wrote:
> >
> > On Fri, Nov 25, 2022 at 11:59 AM Paul Koning via Gcc
> > wrote:
> >>
> >> I'm trying to use fairly recent GCC sources (the gcc-darwin branch to be
> >> precise) to build Ada,
Hi Paul,
> On 25 Nov 2022, at 20:08, Paul Koning via Gcc wrote:
>
>> On Nov 25, 2022, at 3:03 PM, Andrew Pinski wrote:
>>
>> On Fri, Nov 25, 2022 at 11:59 AM Paul Koning via Gcc wrote:
>>>
>>> I'm trying to use fairly recent GCC sources (the gcc-darwin branch to be
>>> precise) to build Ada
On Fri, Nov 25, 2022 at 3:09 PM Paul Koning via Gcc wrote:
> But in any case, how does that relate to the error messages I got? They
> don't seem to have anything to do with missing compilers, but rather with the
> use of language features too new for the available (downloadable) Gnat.
General
On Nov 25, 2022, Paul Koning via Gcc wrote:
> They don't seem to have anything to do with missing compilers, but
> rather with the use of language features too new for the available
> (downloadable) Gnat.
The gnat1 front-end requires some of the Ada runtime (libgnat)
components. They get built
Hi Paul,
> On 25 Nov 2022, at 20:13, Andrew Pinski via Gcc wrote:
>
> On Fri, Nov 25, 2022 at 12:08 PM Paul Koning wrote:
>>
>>> On Nov 25, 2022, at 3:03 PM, Andrew Pinski wrote:
>>>
>>> On Fri, Nov 25, 2022 at 11:59 AM Paul Koning via Gcc
>>> wrote:
I'm trying to use fairly rec
Snapshot gcc-11-20221125 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20221125/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Dear Martin Liška
Thanks for your research. I have resolved this problem by pass a ddrsize
paramters when build and cacluate the offset used by -fasan-shadow-offset
according that parameter.
Thanks!
B.R.
tao.z...@amlogic.com
Address： Building E5, 2555 Xiupu Road, Pudong District, Shang
25 matches
Mail list logo
