F&B #Trending Recipes

#Trending Recipes   View In The Web  

Re: GSoC 2019

Hello Parashuram, On Tue, Feb 12 2019, Shourya IIT B wrote: > Respected Sir, > >I am Parashuram Shourya from India. Currently, I am doing my > Master’s in Geoinformatics from Centre of Studies in Resources > Engineering(CSRE), > Indian Institute of Technology Bombay(IITB). I have a Bachelo

Re: Question: after gcc intallation

Oh and this is the wrong mailing list, please use gcc-h...@gcc.gnu.org instead. On Wed, 13 Feb 2019 at 17:11, Jonathan Wakely wrote: > > On Wed, 13 Feb 2019 at 16:18, Chang-Hsin Daniel Chen > wrote: > > > > Hi GCC, > > > > This is Daniel. I use fedora 29 and have install gcc-8.2.0 into the syste

Re: Question: after gcc intallation

On Wed, 13 Feb 2019 at 16:18, Chang-Hsin Daniel Chen wrote: > > Hi GCC, > > This is Daniel. I use fedora 29 and have install gcc-8.2.0 into the system. Why? Fedora 29 already has GCC 8.2.1 How did you install it? What commands did you run? >However, I still cannot see GCC on the list what I do

Question: after gcc intallation

Hi GCC, This is Daniel. I use fedora 29 and have install gcc-8.2.0 into the system. However, I still cannot see GCC on the list what I do "module av". I have added the path of the gcc directory into .bashrc. However, nothing changes. "export PATH=$PATH:/..." "export LD_LIBRARY_PATH=$PATH:/..."

RE: Warning: unpredictable: identical transfer and status registers --`stxr w4,x5,[x4] using aarch64 poky gcc 8.3

Hi, On Wed, 13 Feb 2019, Peng Fan wrote: > So the fix should be the following, right? Yup. Ciao, Michael.

RE: Warning: unpredictable: identical transfer and status registers --`stxr w4,x5,[x4] using aarch64 poky gcc 8.3

> -Original Message- > From: Andreas Schwab [mailto:sch...@suse.de] > Sent: 2019年2月13日 21:59 > To: Peng Fan > Cc: gcc@gcc.gnu.org; james.greenha...@arm.com; n...@arm.com; > jailhouse-...@googlegroups.com; will.dea...@arm.com; Catalin Marinas > > Subject: Re: Warning: unpredictable: iden

RE: Warning: unpredictable: identical transfer and status registers --`stxr w4,x5,[x4] using aarch64 poky gcc 8.3

Hi Michael, > -Original Message- > From: Michael Matz [mailto:m...@suse.de] > Sent: 2019年2月13日 22:28 > To: Peng Fan > Cc: gcc@gcc.gnu.org; james.greenha...@arm.com; n...@arm.com; > jailhouse-...@googlegroups.com; will.dea...@arm.com; Catalin Marinas > > Subject: Re: Warning: unpredictabl

Re: Warning: unpredictable: identical transfer and status registers --`stxr w4,x5,[x4] using aarch64 poky gcc 8.3

Hi, On Wed, 13 Feb 2019, Peng Fan wrote: > asm volatile ( > "ldxr %3, %2\n\t" > "ands %1, %3, %4\n\t" > "b.ne 1f\n\t" > "orr%3, %3, %4\n\t" > "1:\n\t"

Re: Warning: unpredictable: identical transfer and status registers --`stxr w4,x5,[x4] using aarch64 poky gcc 8.3

On Feb 13 2019, Peng Fan wrote: > static inline int test_and_set_bit(int nr, volatile unsigned long *addr) > { > u32 ret; > u64 test, tmp; > > BITOPT_ALIGN(nr, addr); > > /* AARCH64_TODO: using Inner Shareable DMB at the moment, > * revisit when we will de

RE: Warning: unpredictable: identical transfer and status registers --`stxr w4,x5,[x4] using aarch64 poky gcc 8.3

> -Original Message- > From: jailhouse-...@googlegroups.com > [mailto:jailhouse-...@googlegroups.com] On Behalf Of Segher Boessenkool > Sent: 2019年2月13日 17:11 > To: Peng Fan > Cc: gcc@gcc.gnu.org; james.greenha...@arm.com; n...@arm.com; > jailhouse-...@googlegroups.com; will.dea...@arm.c

Re: question about inlining long call sequence

On Tue, Feb 12, 2019 at 6:16 PM Martin Jambor wrote: > > On Tue, Feb 12 2019, Bin.Cheng wrote: > > Hi, > > When reading inlining code in GCC, I wonder if we have size heuristics > > to limit inlining long call sequence? For example, for call sequence > > A -> B -> C -> D -> ... -> X -> Y -> Z > >

Re: Warning: unpredictable: identical transfer and status registers --`stxr w4,x5,[x4] using aarch64 poky gcc 8.3

OneWed, Feb 13, 2019 at 07:13:21AM +, Peng Fan wrote: > We met an issue when building a piece jailhouse hypervisor code, "stxr %w0, > %3, %2\n\t" is > compiled as "stxr w4,x5,[x4]" which triggers the warning > "Warning: unpredictable: identical transfer and status registers" This is not a

named address space problem

Hi ! While porting a GCC 4.9 private port to GCC 7, I've encountered an issue with named address space support. I have defined the following target macros: #define K1_ADDR_SPACE_UNCACHED 1 #define K1_ADDR_SPACE_CONVERT 2 TARGET_ADDR_SPACE_LEGITIMATE_ADDRESS_P (returns false for CONVERT, regul