Re: What is going on here with fixup_cfg?
On Wed, May 5, 2021 at 12:19 AM Gary Oblock via Gcc wrote:
>
> My jaws hit the floor when I saw this bug:
>
> psimplex.c: In function ‘master.constprop’:
> psimplex.c:124:6: error: non-trivial conversion in ‘constructor’
> 124 | void master(network_t *net, int num_threads)
> | ^
> struct _modif_basket *[4061]
> struct _modif_basket *[4061]
> struct _modif_basket *[4061]
> struct _modif_basket *[4061]
> # .MEM_111 = VDEF <.MEM_103>
> perm ={v} {CLOBBER};
> during GIMPLE pass: fixup_cfg
> psimplex.c:124:6: internal compiler error: verify_gimple failed
> 0x12da3a4 verify_gimple_in_cfg(function*, bool)
> ../../sources/gcc/tree-cfg.c:5482
> 0x10e69f8 execute_function_todo
> ../../sources/gcc/passes.c:1992
> 0x10e598b do_per_function
> ../../sources/gcc/passes.c:1640
> 0x10e6be8 execute_todo
> ../../sources/gcc/passes.c:2046
>
> I've included a bit too much stuff but the bit that
> confused the heck out of me was the
>
> struct _modif_basket *[4061]
> struct _modif_basket *[4061]
>
> associated with the clobber.
>
> I've been banging away for few days
> trying to make the types associated with
> the left and right hand sides of this clobber
> agree and now it's complaining about that
> too?!
>
> The type of perm has changed so what
> should right hand type be now?
The same type? ;) Try dumping with -uid which
will get you type and decl UIDs printed. Maybe
you have multple instances of 'struct _modif_basket'.
> When
> dumping out other instances of clobber,
> the instances all matched so why should
> this need to be different?
>
> Thanks,
>
> Gary
>
>
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
> for the sole use of the intended recipient(s) and contains information that
> is confidential and proprietary to Ampere Computing or its subsidiaries. It
> is to be used solely for the purpose of furthering the parties' business
> relationship. Any unauthorized review, copying, or distribution of this email
> (or any attachments thereto) is strictly prohibited. If you are not the
> intended recipient, please contact the sender immediately and permanently
> delete the original and any copies of this email and any attachments thereto.
[Alert]: ASSIGNMENT ($500.00)
Dear Prospective Panelist, You have been selected as a Customer Satisfaction Analyst to participate in our short exclusive 10-15 minutes paid project study on Walmart,Walgreens & CVS stores within your area. REWARDS: You will earn $500.00 for each completed survey project. SURVEY [#53779-1001] DIRECTIVES: LifePoints Research will send you a check to cover the expense and compensation for your first survey project. You will visit the nearest Walmart/Walgreens/CVS store within your area to conduct your evaluation survey by utilizing the store products/transfer services to rate their customer satisfaction standards, associate skills and facility management. As a survey panelist, you will act as a potential customer at the assigned Walmart/Walgreens/CVS store and complete your survey questionnaire report on the quality of store services and efficiency of associates in order to submit a fair and unbiased rating in your survey report. _ Complete Your Survey Participant Profile > ** *Full Name: *Complete Mailing Address: *Phone #(cell): *Work Experience: *Alternate Email: * THANK YOU - WE APPRECIATE AND VALUE YOUR PARTICIPATION! Sincerely, LifePoints Research, Inc.® 85 Broadway St New York, NY 10004 Attn: Scott Richards (Operations Manager) [P: (585) 735-7030]
Re: Gcc Digest, Vol 15, Issue 5
Hi, On Wed, May 05 2021, Gary Oblock via Gcc wrote: > I've got to say appearances can be deceptive > in GCC and struct _modif_basket *[4061] is not > necessarily equal to struct _modif_basket *[4061] > even though the printed representation is > the same... In these cases it is handy to use the -fdump-.*-uid dumps, as for example in -fdump-tree-release_ssa-uid When invoking dumping from the code, the flag for it TDF_UID. Martin
[RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (May 6, 2021)
Hi all, There is the agenda for tomorrow's meeting. If you have topics to discuss or share, please let me know and I can add them to the agenda. ## Agenda: 1. Status update for B, K, P, Zce, Zfinx extensions. 2. Zfinx ABI discussion 3. Revisit todo-list in the former code-speed-opt repos[1]. 4. Discuss the status of CI Infrastructure for RISC-V backend and how to improve/contribute. 5. AOB [1] https://github.com/riscv/riscv-code-speed-optimization/blob/main/projects/gcc-optimizations.adoc https://calendar.google.com/calendar/ical/lm5bddk2krcmtv5iputjgqvoio%40group.calendar.google.com/public/basic.ics BEIJING, China 11:00pThu, May 6 2021 12:00aFri, May 7 2021 PDT/PST, Pacific Daylight Time (US) 8:00aThu, May 6 2021 9:00aThu, May 6 2021 LONDON, United Kingdom, England 4:00pThu, May 6 2021 5:00pThu, May 6 2021 Join Zoom Meeting https://zoom.com.cn/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZjZZMHhRQT09 Meeting ID: 893 9360 0951 Passcode: 899662 Find your local number: https://zoom.com.cn/u/kWo4yMmVQ -- Best wishes, Wei Wu (吴伟)
gcc-8-20210505 is now available
Snapshot gcc-8-20210505 is now available on https://gcc.gnu.org/pub/gcc/snapshots/8-20210505/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-8 revision 06d75273ff7bb7af72ae83abef858c079245b602 You'll find: gcc-8-20210505.tar.xzComplete GCC SHA256=769b53278c51cd39f4ec8c184d760732020887615931d590407465916727513a SHA1=17fa0814b9daca3163ab3469b8ed1f708144cc12 Diffs from 8-20210428 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-8 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
